Skip to content

Conversation

@tautschnig
Copy link
Collaborator

@tautschnig tautschnig commented Nov 30, 2025

Please review commit-by-commit.

Fixes: #8714
Fixes: #7957

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@tautschnig tautschnig force-pushed the refine-symex-pointer-unsoundness branch from 889225b to 2dc63d4 Compare November 30, 2025 18:43
@codecov
Copy link

codecov bot commented Nov 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.93%. Comparing base (4fe3ade) to head (c954ba7).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #8780   +/-   ##
========================================
  Coverage    79.93%   79.93%           
========================================
  Files         1698     1698           
  Lines       187698   187708   +10     
  Branches        73       73           
========================================
+ Hits        150034   150050   +16     
+ Misses       37664    37658    -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@tautschnig tautschnig force-pushed the refine-symex-pointer-unsoundness branch from 2dc63d4 to 9d4ffaf Compare November 30, 2025 20:13
We cannot soundly handle pointer offsets that are shared across threads,
and will reject this in future to avoid unsound verification results.
Here, however, the pointer offsets are not actually shared, so we can
safely mark them `__CPROVER_thread_local`.
…ed pointers

Reading and writing pointers is not not itself unsound, only the
interaction with value sets may cause unsound results. Hence, do not
reject programs that never dereference a shared pointer.

Fixes: diffblue#8714
Fixes: diffblue#7957
Shared pointers may be updated in yet-to-be-executed threads.
@tautschnig tautschnig force-pushed the refine-symex-pointer-unsoundness branch from c954ba7 to d48dfd7 Compare December 1, 2025 17:29
@tautschnig tautschnig marked this pull request as ready for review December 1, 2025 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants