[Bug tree-optimization/34038] 176.gcc segfaults when compiled with -O2 -ftree-vectorize -maltivec

[janis at gcc dot gnu dot org]

------- Comment #2 from janis at gcc dot gnu dot org  2007-11-29 19:01 -------
I can reproduce the failure with revision 130507 on a p970 system.  I compile
176.gcc with "-m32 -O3 -maltivec" and execute that benchmark program with test
input.

My list of vectorized loops is the same except that reload1.c:2433 is reported
twice:

elm3b145% fgrep 'LOOP VECTORIZED' reload.c.104t.vect
reload.c:3231: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload.c:3257: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload.c:2352: note: LOOP VECTORIZED.
elm3b145% fgrep 'LOOP VECTORIZED' reload1.c.104t.vect
reload1.c:2433: note: LOOP VECTORIZED.
reload1.c:3968: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:3749: note: LOOP VECTORIZED.
reload1.c:784: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:697: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:3623: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:3617: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:2447: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:2433: note: LOOP VECTORIZED.(get_loop_exit_condition 
reload1.c:474: note: LOOP VECTORIZED.

It shouldn't make any difference, of course, but I normally build GCC using
--with-cpu=default32 and I think you don't do that; I'll try without it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34038