public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101267] New: [12 Regression] ICE in vect_is_simple_use when building 521.wrf_r with -Ofast -march=znver2
Date: Wed, 30 Jun 2021 09:37:28 +0000	[thread overview]
Message-ID: <bug-101267-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101267
           Summary: [12 Regression] ICE in vect_is_simple_use when
                    building 521.wrf_r with -Ofast -march=znver2
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

gfortran -c -o module_fdda_psufddagd.fppized.o -I. -I./netcdf/include -I./inc
-Ofast -march=znver2 -fdump-statistics-stats -std=legacy -fconvert=big-endian
-fno-openmp -g0 module_fdda_psufddagd.fppized.f90
during GIMPLE pass: slp
module_fdda_psufddagd.fppized.f90:553:21:

  553 |    SUBROUTINE sfddagd(itimestep,dx,dt,xtime,  &
      |                     ^
internal compiler error: in vect_is_simple_use, at tree-vect-stmts.c:11422
0x75f7e4 vect_is_simple_use(tree_node*, vec_info*, vect_def_type*, tree_node**,
_stmt_vec_info**, gimple**)
        /home/rguenther/src/trunk/gcc/tree-vect-stmts.c:11422
0x110c3a7 vect_check_scalar_mask
        /home/rguenther/src/trunk/gcc/tree-vect-stmts.c:2470
0x110ed97 vectorizable_load
        /home/rguenther/src/trunk/gcc/tree-vect-stmts.c:8500
0x111d53a vect_analyze_stmt(vec_info*, _stmt_vec_info*, bool*, _slp_tree*,
_slp_instance*, vec<stmt_info_for_cost, va_heap, vl_ptr>*)
        /home/rguenther/src/trunk/gcc/tree-vect-stmts.c:10836
0x115a60b vect_slp_analyze_node_operations_1
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:4430
0x115a60b vect_slp_analyze_node_operations
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:4589
0x115c818 vect_slp_analyze_operations(vec_info*)
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:4824
0x1160470 vect_slp_analyze_bb_1
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:5702
0x1160470 vect_slp_region
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:5748
0x11619b8 vect_slp_bbs
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:5898
0x1161db4 vect_slp_function(function*)
        /home/rguenther/src/trunk/gcc/tree-vect-slp.c:5984
0x1167e02 execute
        /home/rguenther/src/trunk/gcc/tree-vectorizer.c:1445
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	other threads:[~2021-06-30  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  9:37 rguenth at gcc dot gnu.org [this message]
2021-06-30  9:37 ` [Bug tree-optimization/101267] " rguenth at gcc dot gnu.org
2021-06-30  9:41 ` rguenth at gcc dot gnu.org
2021-06-30  9:44 ` marxin at gcc dot gnu.org
2021-06-30 10:03 ` rguenth at gcc dot gnu.org
2021-06-30 10:36 ` rsandifo at gcc dot gnu.org
2021-06-30 11:30 ` rguenth at gcc dot gnu.org
2021-06-30 14:40 ` cvs-commit at gcc dot gnu.org
2021-06-30 14:40 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101267-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).