This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 3.[01] C++ Testing: Support -mabi=64
- To: ro at TechFak dot Uni-Bielefeld dot DE
- Subject: Re: 3.[01] C++ Testing: Support -mabi=64
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Sun, 3 Jun 2001 20:41:25 -0400 (EDT)
- Cc: david dot billinghurst at riotinto dot com, gcc-patches at gcc dot gnu dot org, oldham at codesourcery dot com
> From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
>
> Jeffrey Oldham writes:
>
> > > Unfortunately, this patch has just the opposite effect for me ;-)
> > > Before it went it, I could successfully test both N32 and N64 ABIs
> > > on IRIX 6.2 and 32-bit and 64-bit on Solaris 8. I'm using command
> > > lines like this:
> > >
> > > make RUNTESTFLAGS='--target_board "unix{,-mabi=64}"' check
> > > or
> > > make RUNTESTFLAGS='--target_board "unix{,-m64}"' check
> >
> > How should -mabi=64 tests be run? I was using
> >
> > make -k RUNTESTFLAGS="--tool_opts '-mabi=64'" check-g++
>
> This should work to specify a single alternative option. To run the
> testsuite with several different options, you need the variant I use,
> which
> is documented in the FAQ:
>
> http://gcc.gnu.org/fom_serv/cache/21.html
>
> So both variants need to continue working.
> Rainer
So what was the resolution of this problem? I'm having the same issue
Rainer had using the --target_board option, as shown here in the
following test results on irix6.2:
http://gcc.gnu.org/ml/gcc-testresults/2001-06/msg00071.html
I think most of the g++ and libstdc++-v3 tests failures with -mabi=64
I'm seeing are because of this problem.
Thanks,
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions