On 23 September 2016 at 17:55, Matthew Fortune
<matthew.fort...@imgtec.com> wrote:
> Doug Gilmore <doug.gilm...@imgtec.com> writes:
>> > From: Richard Biener [rguent...@suse.de]
>> > Sent: Thursday, September 22, 2016 12:43 AM
>> > To: Doug Gilmore
>> > Cc: gcc-patches@gcc.gnu.org; rgue...@gcc.gnu.org
>> > Subject: RE: [PATCH] Fix PR tree-optimization/77654
>> >
>> > On Wed, 21 Sep 2016, Doug Gilmore wrote:
>> >
>> > ...
>> > > Sorry I that missed point.  I glossed your comment "addr_base should
>> > > always be a pointer", causing me to go off into the weeds.
>> > >
>> > > New patch attached.
>> >
>> > Ok if successfully bootstrapped / tested.
>> >
>> > Thanks,
>> > Richard.
>> The change bootstrapped on X86_64 and the several "make check" errors
>> also appeared in latest archived mail message to gcc-testresults.
>
> Committed as r240439.
>

Since this commit, I've noticed ICE on arm target:
FAIL: gcc.dg/params/blocksort-part.c -O3 --param prefetch-latency=0
(internal compiler error)
FAIL: gcc.dg/params/blocksort-part.c -O3 --param prefetch-latency=0
(test for excess errors)
Excess errors:
/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/testsuite/gcc.dg/params/blocksort-part.c:116:6:
internal compiler error: in duplicate
_ssa_name_ptr_info, at tree-ssanames.c:630
0xd5a972 duplicate_ssa_name_ptr_info(tree_node*, ptr_info_def*)
        /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/tree-ssanames.c:630
0xcac0e0 issue_prefetch_ref
        /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/tree-ssa-loop-prefetch.c:1168
0xcad89f issue_prefetches
        /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/tree-ssa-loop-prefetch.c:1195
0xcad89f loop_prefetch_arrays
        /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/tree-ssa-loop-prefetch.c:1928
0xcae722 tree_ssa_prefetch_arrays()
        /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/tree-ssa-loop-prefetch.c:1992


--target arm-none-linux-gnueabihf --with-cpu=cortex-a9
--wihth-fpu=neon-fp16 --with-mode=arm

I'm not sure the cpu/fpu/mode settings are mandatory but at least in this case
the compiler ICEs.

Christophe


> (Fixed whitespace/tab issue in the code and incorrect file in changelog)
>
> I can't progress the bug status. Who does that normally?
>
> Matthew

Reply via email to