Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identifying independent unsafe behaviors #112

Open
vaishnaviMG15 opened this issue Aug 13, 2022 · 0 comments
Open

Identifying independent unsafe behaviors #112

vaishnaviMG15 opened this issue Aug 13, 2022 · 0 comments

Comments

@vaishnaviMG15
Copy link
Collaborator

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant