[Bug target/56865] [4.9 regression] FAIL: gcc.dg/vect/vect-96.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1
wschmidt at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Wed Oct 30 15:05:00 GMT 2013
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56865
--- Comment #18 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
spawn /home/wschmidt/gcc/build/gcc-mainline-test2/gcc/xgcc -B/home/wschmidt/gcc
/build/gcc-mainline-test2/gcc/ /home/wschmidt/gcc/gcc-mainline-test2/gcc/testsu
ite/gcc.dg/vect/vect-96.c -fno-diagnostics-show-caret -fdiagnostics-color=never
-maltivec -mvsx -mno-allow-movmisalign -ftree-vectorize -fno-vect-cost-model -
fno-common -O2 -fdump-tree-vect-details -lm -m32 -o ./vect-96.exe
/home/wschmidt/gcc/gcc-mainline-test2/gcc/testsuite/gcc.dg/vect/vect-96.c: In f
unction 'main1':
/home/wschmidt/gcc/gcc-mainline-test2/gcc/testsuite/gcc.dg/vect/vect-96.c:16:5:
internal compiler error: Segmentation fault
0x1068325b crash_signal
/home/wschmidt/gcc/gcc-mainline-test2/gcc/toplev.c:334
0x10c74f90 hash_table<peel_info_hasher, xcallocator>::elements()
/home/wschmidt/gcc/gcc-mainline-test2/gcc/hash-table.h:538
0x10c74f90 traverse<_vect_peel_extended_info*, vect_peeling_hash_get_most_frequ
ent>
/home/wschmidt/gcc/gcc-mainline-test2/gcc/hash-table.h:947
0x10c74f90 vect_peeling_hash_choose_best_peeling
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-vect-data-refs.c:1248
0x10c74f90 vect_enhance_data_refs_alignment(_loop_vec_info*)
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-vect-data-refs.c:1662
0x108cbc53 vect_analyze_loop_2
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-vect-loop.c:1732
0x108cbc53 vect_analyze_loop(loop*)
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-vect-loop.c:1810
0x108e750b vectorize_loops()
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-vectorizer.c:360
0x107f866f tree_loop_vectorize
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-ssa-loop.c:149
0x107f866f execute
/home/wschmidt/gcc/gcc-mainline-test2/gcc/tree-ssa-loop.c:184
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
More information about the Gcc-bugs
mailing list