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: Analysis of g++.dg/bprob/g++-bprob-1.C multilib failures


 > From: Janis Johnson <janis187@us.ibm.com>
 > 
 > On Sat, Dec 28, 2002 at 11:13:14AM -0500, Kaveh R. Ghazi wrote:
 > > 
 > > I'm kind of stuck, since this is a maze of dejagnu stuff.  If someone
 > > has ideas I would appreciate some help on this one.
 > 
 > I wrote the framework for those tests, so perhaps I could figure out
 > what's going on.  I've never used multilibs; is that something I could
 > do with a cross compiler (and simulator) on my i686-pc-linux-gnu laptop
 > while I'm at home during the next few days?  It's cranking away looking
 > for patches that introduced regressions, but it could be put to work
 > doing something else for a while, and I can interrupt my weaving and
 > papermaking and baking and lazing about to try to remember what those
 > tests are doing.
 > Janis

Thanks Janis, that'll be a big help.  While you may be able to
recreate the error with a multilib simulator, I suspect you may be
able to use *any* multipass testsuite run.  For example, one regular
(plain vanilla) pass and one -fPIC pass.  That would work on a native
x86-linux-gnu box and should be much simpler since the cross stuff
won't come into play.  If you have the trunk already built and handy,
as a first guess try:

make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" check-gcc-c++

see if that triggers it for you.  

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


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