https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86944

            Bug ID: 86944
           Summary: ICE in vectorizable_store, at tree-vect-stmts.c:6878
                    on aarch64
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: rdsandiford at googlemail dot com
  Target Milestone: ---

Following ICEs:

$ ./xgcc -B.
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr66449.c
-mstrict-align -Ofast --param vect-epilogues-nomask=1
during GIMPLE pass: vect
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr66449.c: In
function ‘fn1’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr66449.c:8:7:
internal compiler error: in vectorizable_store, at tree-vect-stmts.c:6878
8 | void *fn1(void *p1, void *p2, long p3)
  |       ^~~
0x13a9726 vectorizable_store
        /home/marxin/Programming/gcc/gcc/tree-vect-stmts.c:6878
0x13b36b2 vect_transform_stmt(_stmt_vec_info*, gimple_stmt_iterator*,
_slp_tree*, _slp_instance*)
        /home/marxin/Programming/gcc/gcc/tree-vect-stmts.c:9721
0x13d7831 vect_transform_loop_stmt
        /home/marxin/Programming/gcc/gcc/tree-vect-loop.c:8228
0x13d8585 vect_transform_loop(_loop_vec_info*)
        /home/marxin/Programming/gcc/gcc/tree-vect-loop.c:8450
0x13fef2f try_vectorize_loop_1
        /home/marxin/Programming/gcc/gcc/tree-vectorizer.c:945
0x13ff10d try_vectorize_loop_1
        /home/marxin/Programming/gcc/gcc/tree-vectorizer.c:978
0x13ff1c9 try_vectorize_loop
        /home/marxin/Programming/gcc/gcc/tree-vectorizer.c:995
0x13ff3a5 vectorize_loops()
        /home/marxin/Programming/gcc/gcc/tree-vectorizer.c:1077
0x128e3e1 execute
        /home/marxin/Programming/gcc/gcc/tree-ssa-loop.c:414
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

Reply via email to