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.

Sign up for GitHub

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

Jump to bottom

Per-harness code generation #1855

Closed
celinval opened this issue Nov 4, 2022 · 0 comments · Fixed by #2439
Closed

Per-harness code generation #1855

celinval opened this issue Nov 4, 2022 · 0 comments · Fixed by #2439
Assignees
@celinval
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.

Comments

@celinval
Copy link
Contributor

celinval commented Nov 4, 2022

Requested feature: Generate code on a per-harness basis instead of aggregating the reachable code for all harnesses.
Use case: Improve the verification performance since goto-instrument may not be able to slice some stuff that is actually unreachable. See #1659 for an example on how adding a second harness can interfere with the time of the first.
Link to relevant documentation (Rust reference, Nomicon, RFC):
@fzaiser fzaiser mentioned this issue Nov 8, 2022
Merged
4 tasks
@celinval celinval self-assigned this Nov 8, 2022
@tedinski tedinski added the [C] Feature / Enhancement A new feature request or enhancement to an existing feature. label Nov 14, 2022
This was referenced May 9, 2023
Merged
Merged
@celinval celinval assigned feliperodri and celinval and unassigned celinval and feliperodri May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@celinval celinval

Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.
Projects
No open projects
Kani 0.17
Status: Done
Kani 0.18
Status: Done
Kani 2023-05-29
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Perform reachability analysis on a per-harness basis celinval/kani-dev
3 participants
@tedinski @feliperodri @celinval