Question

Consider a situation. We have some specific C++ compiler, a specific set of compiler settings and a specific C++ program.

We compile that specific programs with that compiler and those settings two times, doing a “clean compile” each time.

Should the machine code emitted be the same (I don’t mean timestamps and other bells and whistles, I mean only real code that will be executed) or is it allowed to vary from one compilation to another?

Answer 1

The C++ standard certainly doesn’t say anything to prevent this from happening. In reality, however, a compiler is normally deterministic, so given identical inputs it will produce identical output.

The real question is mostly what parts of the environment it considers as its inputs — there are a few that seem to assume characteristics of the build machine reflect characteristics of the target, and vary their output based on “inputs” that are implicit in the build environment instead of explicitly stated, such as via compiler flags. That said, even that is relatively unusual. The norm is for the output to depend on explicit inputs (input files, command line flags, etc.)

Offhand, I can only think of one fairly obvious thing that changes “spontaneously”: some compilers and/or linkers embed a timestamp into their output file, so a few bytes of the output file will change from one build to the next–but this will only be in the metadata embedded in the file, not a change to the actual code that’s generated.