-
Notifications
You must be signed in to change notification settings - Fork 6
zola, tamarin-prover: fix reproducibility (parallel codegen order; compile-time clock) #525
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: gominimal/pkgs
Length of output: 2791
🏁 Script executed:
Repository: gominimal/pkgs
Length of output: 29554
🌐 Web query:
Rust rustc -C symbol-mangling-version=v0 compilation-session hash legacy mangling reproducible builds official documentation💡 Result:
The v0 symbol mangling scheme is the current standard for symbol name encoding in the Rust compiler (rustc) [1][2]. It was developed to replace the legacy mangling scheme, which relied on C++-style mangling and compiler-internal structures [3][2]. Key aspects of the v0 scheme include: Consistency and Reproducibility: The v0 format is designed to be unambiguous and platform-independent, with a consistent definition that does not depend on compiler-internal states or pretty-printing [4][3]. By restricting symbols to a consistent character set (A-Z, a-z, 0-9, _), it improves compatibility across different toolchains and platforms [4][2]. Reproducible Builds: While v0 provides a more stable and decodable symbol format than the legacy scheme, reproducibility can still be affected by other compiler settings [5]. For example, the use of -Cmetadata in rustc can influence the disambiguators present in mangled symbols [5]. Discussions in the Rust community note that because v0 symbols may include hashes to distinguish crate versions or generic instantiations, changes in metadata can still lead to differences in the generated symbol names and, consequently, the order of symbols in an executable [5]. Compilation Control: The mangling version can be controlled using the compiler flag -Csymbol-mangling-version [1]. - v0: The current standard, which provides reversible encoding for generic parameters and is more efficient/standardized [4][6]. - legacy: The older scheme, which is available on some versions of the compiler (primarily for backward compatibility or as an escape hatch) but is generally deprecated [1][2][7]. Official documentation on the v0 format is maintained in The rustc book, which details the encoding, the motivation behind the change (RFC 2603), and how the scheme handles various Rust entities [4][3][1]. Tooling such as rustfilt or the rustc-demangle crate is recommended for decoding these symbols [1].
Citations:
🏁 Script executed:
Repository: gominimal/pkgs
Length of output: 550
Create a private temporary directory for the entropy shim.
/tmp/detrand.cand/tmp/detrand.souse predictable shared paths. A local user can replace these files and causeLD_PRELOADto load attacker-controlled code. Use a privatemktemp -ddirectory and clean it withtrap.The cited double-build report is absent. Keep
-C codegen-units=1;AGENTS.mdrequires it when.textor.rodatadiffers, and this script documents such differences. Do not removesymbol-mangling-version=v0without a reproducibility comparison.🤖 Prompt for AI Agents