gcc-64 on HP-UX 11.00

[John David Anglin]

>  > Jeff, I will send you gv.i offline so that you can look at the problem
>  > in more detail.
> Thanks.  Here's the patch that allows me to compile gv.i without any
> problems.  I've bootstrapped both 32bit and 64bit.  I've built perl
> both 32bit and 64bit.
> 
> I've also examined the register costing for gv.i and it looks a hell of
> a lot better.  With an older PA64 compiler (which exhibits this bug) I
> end up with 25 registers that prefer FPREGS or GENERAL_OR_FP_REGS,
> including the problematical pseudos we've been looking at.
> 
> With my fix only only 9 registers want FPREGS or GENERAL_OR_FP_REGS and
> they're all reasonable requests for those classes.

I agree that the costs and prefs look better.  I'm concerned
about the costs for the class GENERAL_OR_FP_REGS.  It's still
not clear why a FP register was selected.

> I'm pretty confident the patch is correct, but you indicated you went
> down this path and it didn't sound like you had much success (though it
> appeared you made other changes in how 'T' has handled).

Following my mail last night, I again implemented what I described.
I did a complete 64bit build and also successfully built perl 64bit.
I think that the problem I had originally with this approach was
just too much midnight oil.

> Anyway, here's the patch.  I'll leave it up to you to decide if we want
> to recommend this for 3.1.

I'll try a build with -mpa-risc-2-0 and decide.  It's a regression
but it only affects PA2.0 PIC code.  My feeling is that the patch
is safe but I have been surprised before.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)