java_static_lifetime_init: Deterministic order of initialisation #6093
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Much like the C front-end, ensure that the collection of objects of
static lifetime is initialised in a fixed order, based on their names.
Previously, the (unspecified) order in an unordered set and unordered
map determined the sequence of instructions being generated, which
resulted in jdiff regression tests sometimes failing. Those failures
were caused by __CPROVER_initialize sometimes showing up among the list
of goto functions that differed.
The functional change is the second commit, the first just does the refactoring to make the second commit as small (and as easy to review) as possible.