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

figure out how to handle noret #36

Open
williballenthin opened this issue Jun 24, 2019 · 0 comments
Open

figure out how to handle noret #36

williballenthin opened this issue Jun 24, 2019 · 0 comments

Comments

@williballenthin
Copy link
Owner

do we assume call don't return until we can prove that they do?

or do we backtrack and remove code once we've found a function is noret?

gut feeling is that the cleanup strategy is easier for analysis passes, cause its one less thing to worry about. but it means that we need robust code cleanup logic.

where do we track the noret attribute?

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