PVS Studio warning fixes

[FeralChild64]

Description

Fixed few warnings.

Checklist

I have:

• followed the project's contributing guidelines and code of conduct.
• performed a self-review of my code.
• commented on the particularly hard-to-understand areas of my code.
• split my work into well-defined, bisectable commits, and I named my commits well.
• applied the appropriate labels (bug, enhancement, refactoring, documentation, etc.)
• checked that all my commits can be built.
• confirmed that my code does not cause performance regressions (e.g., by running the Quake benchmark).
• added unit tests where applicable to prove the correctness of my code and to avoid future regressions.
• made corresponding changes to the documentation or the website according to the documentation guidelines.
• locally verified my website or documentation changes.

[kcgen]

Reviewed commit by comment, all looks great.
First time below 160 on the PVS front!

Created with:

git log --pretty=format:"%h %ad" --date=short --follow -- "$1" | \
while read commit_hash commit_date; do
  git show "$commit_hash" -- "$1" | grep "$2" | sed "s/^/$commit_date - /"
done

./line_history.sh .github/workflows/pvs-studio.yml "^+.*MAX_BUGS:" \
 | tac \
 | sed 's/ - +          MAX_BUGS: /,/g' \
 > pvs_bugs.csv

And to see when we updated PVS Studio:

.github/workflows/pvs-studio.yml "^+.*debfile:" | tac

[FeralChild64]

At some point we’ll need to dig into the CPU emulation code. There is about 60 warning originating there.

[kcgen]

At some point we’ll need to dig into the CPU emulation code:

@FeralChild64, at the code table:

[kcgen]

(I love that old pic of a kid digging into pancakes :-)