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

Tag Theorem and LLVMSpec values that were proved by unsound means #1093

Open
brianhuffman opened this issue Feb 26, 2021 · 1 comment
Open
Labels
type: enhancement Issues describing an improvement to an existing feature or capability
Milestone

Comments

@brianhuffman
Copy link
Contributor

Whenever we produce a Theorem, LLVMSpec, or JVMSpec value as the result of a proof command, it should be specially marked as "unsafe" if any of the lemmas or proof tactics used to produce it were themselves "unsafe". In particular, anything proved using assume_unsat or llvm_unsafe_assume_spec should be marked as unsafe.

In addition to a single "unsafe" bit, we may also wish to record more detailed information about what the sources of the unsafeness were.

This information would be useful to display as part of a verification summary (see also #643).

@brianhuffman brianhuffman added the type: enhancement Issues describing an improvement to an existing feature or capability label Feb 26, 2021
@robdockins
Copy link
Contributor

This is closely related to #1136

@sauclovian-g sauclovian-g added this to the 2025T1 milestone Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Issues describing an improvement to an existing feature or capability
Projects
None yet
Development

No branches or pull requests

3 participants