Skip to content

Conversation

@sim642
Copy link
Member

@sim642 sim642 commented Nov 12, 2025

This is a point in #1722.
For example, this will produce a witness with invariants containing our fictitious __annonCompField offsets:

./goblint --conf conf/svcomp.json --set ana.specification ../sv-benchmarks/c/properties/unreach-call.prp --set exp.architecture 64bit ../sv-benchmarks/c/intel-tdx-module/tdg_mr_report__expected__cover_entry_havoc_memory.i

These should be skipped in witness invariant generation: we can keep the invariant, but just remove such components in the offsets because the following non-anonymous field is supposed to uniquely determine the actual field.

However, there's still a problem: many LDV tasks are CIL-ed and have such field explicitly. There they must remain, but I'm not sure how to differentiate this.
Maybe we just have to exclude all such invariants, instead of trying to adapt them.

@sim642 sim642 added bug sv-comp SV-COMP (analyses, results), witnesses labels Nov 12, 2025
@sim642 sim642 marked this pull request as draft November 14, 2025 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug sv-comp SV-COMP (analyses, results), witnesses

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants