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

Disable race analyses for other ConcurrencySafety properties #1661

Open
sim642 opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1667
Open

Disable race analyses for other ConcurrencySafety properties #1661

sim642 opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1667
Assignees
Labels
good first issue performance Analysis time, memory usage sv-comp SV-COMP (analyses, results), witnesses
Milestone

Comments

@sim642
Copy link
Member

sim642 commented Jan 23, 2025

We realized a little bit of silliness in our SV-COMP setup:

  1. Our svcomp confs have always enabled some of our specialty race analyses like region and symblocks to best work on our submitted regression tests.
  2. The autotuner was added to disable all concurrency analyses for single-threaded programs, but did not further distinguish by property.
  3. Later some per-property autotuning was refactored, but nothing data-race–specific was still done.

The point is that we should disable our specialty race analyses for unreach-call, no-overflow and valid-memsafety analyses in ConcurrencySafety.
In particular, the region analysis is notorious for using a single flow-insensitive unknown which essentially causes everything to depend on everything. This might be quite harmful to performance when we're not trying to prove race-freedom anyway.

@sim642 sim642 added good first issue performance Analysis time, memory usage sv-comp SV-COMP (analyses, results), witnesses labels Jan 23, 2025
@sim642 sim642 added this to the SV-COMP 2026 milestone Jan 23, 2025
@karoliineh karoliineh self-assigned this Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue performance Analysis time, memory usage sv-comp SV-COMP (analyses, results), witnesses
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants