This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: old intentional gcc bug?



On Jun 24, 2007, at 16:20, Eric Botcazou wrote:
Indeed. It would be interesting to confirm whether or not a copy of gcc
bootstrapped with a non-gcc compiler matched byte-for-byte with a copy
of gcc bootstrapped from gcc.

I just made the experiment on an old SPARC/Solaris 2.5.1 machine and they
differ (cc is Sun C 5.0 and gcc is GCC 3.4.3):

Still, if you use these two bootstrapped, slightly different compilers as base for a fresh bootstrap in a new build directory, you'll likely get identical results and that would still prove that there is no self-propagating back door in GCC on that configuration.

The differences you are seeing now are likely caused by differences in
autoconf configuration for the case of GCC compiler versus non-GCC compiler.
While these shouldn't propagate to the final binary, it's easy for some
things to slip through. There's no real incentive to work hard to prevent
that from happening.


-Geert


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]