This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/14650] Testsuite failures with -mabi=64 in compile/20031023-1.c, 20031023-2.c and 20031023-3.c
- From: "ghazi at caip dot rutgers dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Apr 2004 15:56:15 -0000
- Subject: [Bug target/14650] Testsuite failures with -mabi=64 in compile/20031023-1.c, 20031023-2.c and 20031023-3.c
- References: <20040319143219.14650.ghazi@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ghazi at caip dot rutgers dot edu 2004-04-12 15:56 -------
Subject: Re: Testsuite failures with -mabi=64 in compile/20031023-1.c, 20031023-2.c and 20031023-3.c
Although it's not a GCC bug, still I hate spurious testsuite noise. I
have a patch to solve this waiting for review.
http://gcc.gnu.org/ml/gcc-patches/2004-03/msg01966.html
On reflection my patch may be overkill, and we no longer need it
anyway for attr-ctor1.C, etc. Perhaps a better way to solve the
problem would be to add a check_*_available procedure in
testsuite/lib/target-supports.exp as was recently done for named
sections.
Richard - Can you suggest a minimal C testcase that passes with GAS
but fails with the MIPSpro n64 assembler to check for >4GB frames?
I'll try adding that to the testsuite harness.
If that's overkill, perhaps I could just bypass these tests for n64
regardless of whether we're using GAS.
Thoughts?
--Kaveh
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14650