Every Ada tests fail on the mainline with the following error: /home/pinskia/src/checkin/trunk/objdir/gcc/testsuite/ada/acats/tests/a/a22006b.ada:0: error: bad value (generic) for -mtune= switch
Caused by: 2006-01-19 Jan Hubicka <jh@suse.cz> H.J. Lu <hongjiu.lu@intel.com> Evandro Menezes <evandro.menezes@amd.com> * invoke.texi (generic): Document (i686) Update.
Oh, I don't understand why -mcpu and -mtune don't take the same arguments. Maybe Ada is assuming they do.
I can't duplicate this. See: http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01110.html
Here is the result on Linux/ia32: http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01114.html
I did see the same effect on interal builds of 4.1 with the patches applied, but Honza could not reproduce either. I believe there's some magic going on in that Ada uses the host compiler for some/all tests?
ACATS use the host base compiler for compiling two tools that are used to preprocess test sources. Everything else is done using the just built gnatmake. I can't find special processing for tune/cpu in the Ada sources. Andrew did you add -mtune or something to your copy of gcc/testsuite/ada/acats/run_all.sh? If not could you post a bit more from ada/acats/acats.log? (full gnatmake commands are displayed IIRC)
It looks like an old bug.
I will be that the installed gcc Ada 4.2 compiler was used for "make check", similar to PR 14435. *** This bug has been marked as a duplicate of 14435 ***
Reopen, this is a bug in Ada's checking mechanism and not really in the driver.
Can you remove the installed gcc 4.2 and rerun the Ada tests to see what happens?
Since there are no real regressions, I am changing summary.
This is still a regression, even though the change exposed a latent bug.
It has been this way since March, 2004: http://gcc.gnu.org/ml/gcc-bugs/2004-03/msg00641.html Why do you think it is a regression? *** This bug has been marked as a duplicate of 14435 ***
Because your change exposed it.
It does not matter if it is a latent bug or not. This is still a regression. HJL get that through your head.
It is the identical bug as my old one. Should you reopen my bug report and make this one as duplicate since the detailed analysis is in my bug report?
*** This bug has been marked as a duplicate of 14435 ***