Repository navigation
[ILASM] Add option to produce deterministic outputs #8293
Description
Various .NET compilers started adding /deterministic command line option that makes them produce deterministic output (multiple invocations of the compiler produce byte-for-byte identical outputs for the same input).
This includes fields such as:
- The timestamp hardcoded in the PE header
- The MVID value
- PDB guid
- Full paths to the source files
- Maybe more
Activity
RussKeldorph commentedon Jun 6, 2017
@MichalStrehovsky I get the general goodness of this, but is this blocking anyone's real scenario currently, or is this just something you noticed?
MichalStrehovsky commentedon Jun 6, 2017
@RussKeldorph Just something I noticed. dotnet/corefx#20644 touched a test that relies on a binary that needs to be checked into the CoreFX repo only because the MVID is not stable when IL gets recompiled.
/deterministicwould likely avoid that (people might still have to touch the test when ILASM gets upgraded and something about the algorithm to generate stable MVID changes, but that would likely happen rarely). Definitely Pri3 (up-for-grabs?) issue in my view.ARM64&*NIX: Support for background GC (dotnet#8293)
joemmett commentedon Oct 21, 2021
This would be valuable to the Microsoft C++ team. We have a broad goal to produce bit-for-bit identical build outputs and the lack of a deterministic ilasm is impacting a small number of artifacts we build with this tool.
TIHan commentedon Apr 24, 2023
I have added a deterministic flag
/DETto the Framework's version of ILASM last year. We should be able to easily port those changes over to here.JulieLeeMSFT commentedon Jul 31, 2024
We will not have time to work on this in .NET 9. Moving to .NET 10.
JulieLeeMSFT commentedon Oct 15, 2024
@amanasifkhalid, reassigned the ILAsm issue to you.
[ILASM] Add support for deterministic builds and PDB checksums (dotne…