This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: basic-improvements call for testers
- From: Jan Hubicka <jh at suse dot cz>
- To: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com>
- Cc: Jan Hubicka <jh at suse dot cz>, Zack Weinberg <zack at codesourcery dot com>,gcc at gcc dot gnu dot org
- Date: Mon, 16 Dec 2002 23:55:42 +0100
- Subject: Re: basic-improvements call for testers
- References: <FAC87D7C874EAB46A847604DA4FD5A6457D8F1@crtsmail.corp.riotinto.org>
> The HOST_WIDE_INT stuff is fixed (thanks Zack).
>
> I strongly suspect (see PR audit trail) that PR 8521 is due to patch
>
> Wed Nov 6 18:54:47 2002 Alexandre Oliva <aoliva@redhat.com>
>
> * config/mips/mips.h (ASM_OUTPUT_ADDR_DIFF_ELT): Output
> .gpword/.gpdword for ABI_N32 and ABI_64 too, if using the GNU
> assembler.
> * config/mips/mips.md (tablejump_internal3): Output .cpadd
> before jump on ABI_N32 too.
> (tablejump_internal4): Ditto on ABI_64. Increase maximum
> length to match.
I've just commited the fix for irix6.5 so I can bootstrap now.
It makes GCC to not use PIC relative code for N32 and non-gas
configurations.
Honza
>
> I will work on identifying the cygwin problem today.
>
>
> -----Original Message-----
> From: Jan Hubicka [mailto:jh@suse.cz]
> Sent: Monday, 16 December 2002 8:05 PM
> To: Zack Weinberg
> Cc: Billinghurst, David (CRTS); gcc@gcc.gnu.org
> Subject: Re: basic-improvements call for testers
>
>
> > "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com> writes:
> >
> > > I have two PRs open for BIB.
> > > - 8521: Bootstrap failure on irix6.5
> The irix 6.5 problem seems to be indirectly caused by HOST_WIDE_INT
> stuff - preprocessor expect HOST_WIDE_INT to be wider than WCHAR that
> can be 64bit for irix. Unless someone else will do it, I will debug it
> afternoon.
>
> Honza
> > > - 8331: bootstrap failure in ada/decl.c on cygwin
> >
> > I don't have ready access to either of these platforms. I need you to
> > track down (by binary search on the CVS repo, if necessary) the actual
> > patch which caused each of these bootstrap failures. We can then
> > figure out how to fix it.
> >
> > zw