testcase for hppa64 gcc bug

John David Anglin dave@hiauly1.hia.nrc.ca
Mon Oct 30 12:16:00 GMT 2000


> I think I know what's going on here.  The root of the problem is that
> pa-64.h defines an ARG_POINTER_REGNUM that isn't a fixed reg, and isn't
> eliminable.  The arg_pointer isn't even a call-saved reg.  That breaks a
> number of places in the compiler.
> 
> So I went down the path of trying to fix things properly by defining
> ELIMINABLE_REGS and so on, but I ended in a maze of twisty little passages
> labelled "Unrecognizable instruction", like this one:
> 
> /src/parisc/gcc/gcc/libgcc2.c: In function `__moddi3':
> /src/parisc/gcc/gcc/libgcc2.c:601: Unrecognizable insn:
> (insn 1289 209 1298 (set (reg:SI 50 %fr22)
>         (subreg:SI (plus:DI (reg:DI 30 %r30)
>                 (const_int -272 [0xfffffef0])) 0)) -1 (nil)
>     (nil))
> /src/parisc/gcc/gcc/libgcc2.c:601: Internal compiler error in
> extract_insn, at recog.c:2134
> 
> Anyway, this hack seems to fix it for me.
> 
> 	* rtl.h (ARG_POINTER_INVARIANT): Define as 1 if undef.
> 	* rtlanal.c (rtx_unstable_p): Qualify arg_pointer_rtx match with
> 	ARG_POINTER_INVARIANT.
> 	(rtx_varies_p): Likewise.
> 	(rtx_addr_can_trap_p): Likewise.
> 	* local-alloc.c (function_invariant_p): Likewise.
> 	* loop.c (loop_invariant_p): Likewise.
> 	* tm.texi (ARG_POINTER_INVARIANT): Describe.

I don't think this is the correct fix.  Isn't r29 used for 128 bit
return values?

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


More information about the Gcc-bugs mailing list