You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is any program state maintained by the compiler (e.g., safe offsets for each pointer, etc.) changed by the safety_chk_insn function?
If so, it would be useful to understand the implications of pushing on with program checking even after encountering one unsafe instruction.
If the function is entirely stateless (not changing any program state), it would help noting that down explicitly in a comment.
Is any program state maintained by the compiler (e.g., safe offsets for each pointer, etc.) changed by the
safety_chk_insn
function?If so, it would be useful to understand the implications of pushing on with program checking even after encountering one unsafe instruction.
If the function is entirely stateless (not changing any program state), it would help noting that down explicitly in a comment.
Originally posted by @ngsrinivas in #111 (comment)
The text was updated successfully, but these errors were encountered: