------- Comment #3 from dave at hiauly1 dot hia dot nrc dot ca 2005-12-28
00:13 -------
Subject: Re: FAIL: gfortran.dg/cray_pointers_2.f90 at -O2 and above
> Can you attach the dump from -fdump-tree-vars? I suspect that cray_pointers
> are a bit weird on targets like HPPA since we might not record if it is a
> pointer or not in the integer.
Will do. I can see that register r19 has the frame-related flag set
and r1 in .greg:
(insn 1558 191 195 9 (set (reg:DI 1 %r1)
(mem/f/c:DI (plus:DI (reg/f:DI 30 %r30)
(const_int -432 [0xfffffffffffffe50])) [538 S8 A64])) 119
{*pa.md:4136} (nil)
(nil))
(insn 1559 195 187 9 (set (reg/f:DI 19 %r19)
(mem/f/c:DI (plus:DI (reg/f:DI 30 %r30)
(const_int -600 [0xfffffffffffffda8])) [517 ivtmp___4698+0 S8
A64])) 119 {*pa.md:4136} (nil)
(nil))
(insn 187 1559 192 9 (set (reg:DI 6 %r6 [250])
(plus:DI (reg/f:DI 19 %r19)
(reg:DI 1 %r1))) 158 {*pa.md:4941} (nil)
(nil))
(insn 192 187 199 9 (set (mem/s:SF (reg:DI 6 %r6 [250]) [18 S4 A32])
(reg:SF 50 %fr22 [254])) 123 {*pa.md:4342} (insn_list:REG_DEP_TRUE 191
(insn_list:REG_DEP_TRUE 187 (nil)))
(nil))
This allows the peephole2 optimization to form the insn that causes the segv.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25586
