This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC testsuite differences with and without gas on IRIX 6
- From: Joe Buck <jbuck at synopsys dot com>
- To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Cc: gcc at gcc dot gnu dot org, binutils at sources dot redhat dot com, Eric Christopher <echristo at redhat dot com>
- Date: Thu, 24 Jul 2003 12:29:29 -0700
- Subject: Re: GCC testsuite differences with and without gas on IRIX 6
- References: <16160.11824.994818.739106@xayide.TechFak.Uni-Bielefeld.DE>
On Thu, Jul 24, 2003 at 09:06:24PM +0200, Rainer Orth wrote:
> I've just completed two bootstraps of mainline GCC on IRIX 6.5.20 (N32 ABI
> only) with the native as and gas 2.14.90 with this patch:
>
> http://sources.redhat.com/ml/binutils/2003-07/msg00415.html
>
> The only new testsuite failures with gas are in libjava:
>
> +FAIL: PR295 compilation from source
>
> This test (and a few others) fail due to the following gas warning:
>
> /var/tmp//cc80GL5k.s:19: Warning: .space repeat count is zero, ignored
>
> for this code:
>
> .align 3
> .space 0
> .section .rodata
>
> The warning is from from gas/read.c (s_space), where it is only emitted if
> !flag_mri.
>
> The question is how best to fix this:
>
> * The native as doesn't complain, so one may just remove the gas warning.
>
> * One could ignore the warning via dejagnu's target.exp, but that doesn't
> seem friendly to a normal user seeing that warning when compiling his
> code with GCJ.
>
> * One could change GCC not to emit this useless .space directive in the
> first place?
>
> What are people's preferences here?
It would seem that the simplest solution would be to make gas shut up.
When seeing ".space 0", it could just silently create zero space as it
is told.