GCC Reproducible Builds: Transitioning from -frandom-seed to SOURCE_DATE_EPOCH

Question

Deterministic Binary Generation
Achieving bit-for-bit identical binaries across different build environments in GCC requires neutralizing non-deterministic inputs. While -frandom-seed stabilizes optimization passes, the default expansion of __DATE__ and __TIME__ macros introduces temporal variance.

Path and Timestamp Constraints
To maintain a repeatable development environment, GCC supports the SOURCE_DATE_EPOCH environment variable to override system timestamps. Additionally, absolute paths in DWARF debug information often cause binary divergence between different build machines, necessitating the use of -fdebug-prefix-map.

There is uncertainty regarding the interaction between multiple prefix maps and how they prioritize path replacements when overlapping patterns are defined in the configuration.

How does GCC resolve conflicts when multiple -fdebug-prefix-map flags target the same directory hierarchy?
Does the use of SOURCE_DATE_EPOCH fully supersede the need for specific macro overrides in all optimization levels?

Tasadduq Burney · Answer

Answer
GCC does not define a portable precedence for overlapping -fdebug-prefix-map flags; the effective mapping depends on the GCC version and flag order, so you must test your specific toolchain. SOURCE_DATE_EPOCH fixes the expansion of __DATE__, __TIME__ and usually __TIMESTAMP__, but it does not affect __FILE__, absolute paths in DWARF, build‑id generation, LTO symbol naming or archive metadata, so macro‑level overrides may still be required.
Likely explanation
The overlap handling evolved across GCC releases; early versions used first‑match, later ones switched to last‑match, and the implementation may consult flag order or internal hash tables, making the outcome non‑portable.
Confirmed facts
Setting SOURCE_DATE_EPOCH deterministically replaces the timestamps seen by the preprocessor, but it leaves other sources of nondeterminism untouched. Verified ways to eliminate those are -ffile-prefix-map, -fmacro-prefix-map for __FILE__ and general paths, -fdebug-prefix-map for DWARF, and a stable -frandom-seed when LTO or generated symbol names are present.

List every source tree you need to map and create non‑overlapping -fdebug-prefix-map entries, ordering them from most‑specific to most‑general.
Add -ffile-prefix-map== and/or -fmacro-prefix-map if you want to hide __FILE__.
Export SOURCE_DATE_EPOCH= before invoking GCC.
If your build uses link‑time optimization, set -frandom-seed to a value derived deterministically from the input (e.g., a hash of the source file).
Build twice in separate directories with identical flags, strip the binaries, and compare their SHA‑256 sums.
Use readelf -w or dwarfdump on the output to verify that no absolute paths remain and that the intended prefix replacements appear.
Optionally run gcc -E -dM probe.c to confirm that __DATE__, __TIME__ and __TIMESTAMP__ expand to the fixed values.

Missing diagnostic detail: whether your build enables link‑time optimization (LTO). Knowing this determines if you must retain a deterministic -frandom-seed in addition to SOURCE_DATE_EPOCH.

GCC Reproducible Builds: Transitioning from -frandom-seed to SOURCE_DATE_EPOCH

Deterministic Binary Generation

Path and Timestamp Constraints

1 answer

Answer

Likely explanation

Confirmed facts

Your perspective belongs here.

0 question comments