BOOT_CFLAGS and -fomit-frame-pointer
Joe Buck
Joe.Buck@synopsys.COM
Fri Mar 25 18:58:00 GMT 2005
On Fri, Mar 25, 2005 at 10:45:36PM +1100, Greg Schafer wrote:
> On Fri, Mar 25, 2005 at 12:06:33PM +0100, Eric Botcazou wrote:
>
> > What is wrong exactly? Why should 2 different build processes generate the
> > same executable? Is there a (written) rule about this?
>
> No, there is no written rule. However, some folks (like me) are concerned
> with matters of binary reproducibility, and this subtle change in x86 GCC's
> default behaviour seemed a little suspect (to me at least). Like I said, no
> big deal. If noone else thinks it's a problem, don't worry.
It does seem surprising that the flags used are different, and this kind
of thing might potentially trip up a new GCC developer (who might
experience a Heisenbug when he makes a change and just runs "make" for
a quick test, not noticing that the flags have changed).
But I don't think it raises an issue of binary reproducibility, because
the three-stage bootstrap explicitly tests that the binaries come out byte
for byte identical.
More information about the Gcc
mailing list