This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Re: COME ON! FIXIT! AGAIN: cvs bootstrap failure on hppa2.0w-hp-hpux11.00
- To: Alan Modra <alan at linuxcare dot com dot au>
- Subject: Re: [PATCH] Re: COME ON! FIXIT! AGAIN: cvs bootstrap failure on hppa2.0w-hp-hpux11.00
- From: Jeffrey A Law <law at redhat dot com>
- Date: Tue, 23 Jan 2001 18:19:18 -0700
- cc: Markus Werle <markus at lufmech dot rwth-aachen dot de>, gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <Pine.LNX.4.21.0101231217590.29059-100000@front.linuxcare.com.au>y
ou write:
> That being said, I hit the same problem when trying to bootstrap with the
> native C compiler. Here's the fix:
>
> * config/pa/pa.c (hppa_encode_label): Correct size of alloca
> buffer so we don't overrun it. Don't trim off leading `*'.
>
> Jeff, please note that there are two fixes here. I'm not dead certain of
> the `*' fix, but the code was nonsense as it stood.
I'm curious.
You mentioned this patch broke your builds.
For that to happen you would have had to had a symbol with a "*@" prefix.
That's not supposed to happen.
The generic parts of the compiler add "*" when it finds things like register
names. See make_decl_rtl.
The PA port adds '@' if and only if the symbol in question is a function.
So I don't see how this could possibly break your builds.
jeff