Re: -fpic/-fPIC testresults under sol2.9 & ppclinux trunk

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

 > From: Benjamin Kosnik <bkoz@redhat.com>
 > 
 > >There's a bug here and it needs to be examined.
 > >
 > >It may not be a bug in the library code itself, in which case this
 > >isn't the right list to discuss it on.  Andreas might have uncovered a
 > >bug in cc1plus, or in PCH (you use PCH on mainline for the testsuite
 > >right?), or he may have found a bug in the testsuite harness.
 > 
 > Any of these things, agreed. 
 > 
 > To disable PCH in the testrun, remove PCHFLAGS from
 > libstdc++-v3/testsuite_hooks. PCH enabled/disabled should give the same
 > testresults.
 > -benjamin

Thanks for the pointer, that'll make testing easier.  Sorry, I haven't
had time to check removing PCH flags yet.  (And did you mean
testsuite_flags.in rather than testsuite_hooks?)

However I did manage to reproduce the problem on x86-linux-gnu and
mips-irix6.5, so it does seem to affect our most widely used
platforms.  E.g.:
http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00593.html

Wild guess here, if PCH turns out to be the culprit it may be simply
because the pre-compiled header is generated without regard to the
extra flags used in RUNTESTFLAGS.  E.g. PCH was generated "regular"
and the extra testsuite passes use -fpic or something else which
doesn't match.

Is this possible and would it cause these symptoms?  If so, the
solution may be as simple as removing and regenerating the PCH file
once for each separate testsuite pass with the extra flag(s).  I'm not
familiar enough with the code to diagnose or fix this though.

I'll try taking out PCHFLAGS from testsuite_flags.in tonight and see
if that makes the problem go away.  If it does, we've narrowed the
cause of the problem at least.  I'll let you know.

		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu