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

Generalize input limits for validation #73

Open
ngsrinivas opened this issue Mar 3, 2020 · 0 comments
Open

Generalize input limits for validation #73

ngsrinivas opened this issue Mar 3, 2020 · 0 comments

Comments

@ngsrinivas
Copy link
Collaborator

Commit 7ed85fc introduced a limit to the input range to prevent counterexamples that occur due to overflow of the 64-bit bitvector.

This is believed to be due to integer overflows that happen either in the source program or the sampled program, but not the other. We need to see an example to be concrete about this.

Should we replicate the overflow behaviors that happen in the source in the optimized programs, i.e., optimized(.) == source(.) even when there are overflows in the output within the source program? If not, how does one set the limit for the inputs to the source program while validating the optimized program?

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