This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: old intentional gcc bug?
> 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):
Using built-in specs.
Target: sparc-sun-solaris2.5.1
Configured with: /home/eric/svn/gcc/configure
--prefix=/opt/build/eric/local/gcc --with-gmp=/opt/build/eric/local
--with-mpfr=/opt/build/eric/local --with-local-prefix=/opt/build/eric/local
--enable-languages=c --enable-checking=assert,misc,runtime
Thread model: posix95
gcc version 4.3.0 20070623 (experimental)
sunshine% ls -l gcc.cc/gcc/cc1
-rwxrwxr-x 1 eric eric 47123792 Jun 24 07:38 gcc.cc/gcc/cc1
sunshine% ls -l gcc.gcc/gcc/cc1
-rwxrwxr-x 1 eric eric 47126188 Jun 24 13:40 gcc.gcc/gcc/cc1
Most of the differences seem to come from the .stab section, not sure why.
Independently of this, I'm pretty sure that our configure machinery is
sensitive to the bootstrap compiler.
--
Eric Botcazou