Repository navigation
Conversation
Signed-off-by: Raul Estrada <raulestradaa@gmail.com>
Signed-off-by: Raul Estrada <raulestradaa@gmail.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add support for
StaticandStaticMutoperands in Rustlantis, including scalar static declarations, persistent allocations, and provenance-aware pointer/reference tracking.This is a fresh implementation follow-up to #1245 and partially addresses #1162.
Changes
staticandstatic mutdeclarations.StaticandStaticMutoperands.static_countdisabled by default.Validation
Using nightly-2026-10-11:
The reference-call counts are structural coverage indicators; they do not prove that every reference argument originates
from a static allocation.
Pre-existing local-reference bug
An isolated regression identified a provenance issue with
static_count = 0.For seed 5:
The zero-static regression is now checked automatically by the Miri sweep harness.
Scope
This change focuses on scalar statics and existing pointer/reference types.
Aggregate static initializers, thread-local statics, and arbitrary constant expressions remain outside the current scope.
The generated-program Miri sweep validates Rust execution semantics; it is not a replacement for CUDA CPU/GPU differential testing.
Closes neither #1162 nor the broader static-generation work; this PR partially addresses #1162.