public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97500] New: [11 Regression] ICE in vect_schedule_slp_instance, at tree-vect-slp.c:5094 since r11-3823-g126ed72b9f48f853
Date: Tue, 20 Oct 2020 07:34:30 +0000 [thread overview]
Message-ID: <bug-97500-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97500
Bug ID: 97500
Summary: [11 Regression] ICE in vect_schedule_slp_instance, at
tree-vect-slp.c:5094 since r11-3823-g126ed72b9f48f853
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Since the revision, the following fails:
$ gfortran
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.fortran-torture/execute/pr57396.f90
-O3 -fno-guess-branch-probability -c
during GIMPLE pass: vect
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.fortran-torture/execute/pr57396.f90:30:0:
30 | use testmod
|
internal compiler error: in vect_schedule_slp_instance, at tree-vect-slp.c:5094
0x738c15 vect_schedule_slp_instance
/home/marxin/Programming/gcc/gcc/tree-vect-slp.c:5094
0x10c8a37 vect_schedule_slp_instance
/home/marxin/Programming/gcc/gcc/tree-vect-slp.c:5047
0x10c8a37 vect_schedule_slp_instance
/home/marxin/Programming/gcc/gcc/tree-vect-slp.c:5047
0x10c8a37 vect_schedule_slp_instance
/home/marxin/Programming/gcc/gcc/tree-vect-slp.c:5047
0x10ca782 vect_schedule_slp(vec_info*, vec<_slp_instance*, va_heap, vl_ptr>)
/home/marxin/Programming/gcc/gcc/tree-vect-slp.c:5305
0x10aedb8 vect_transform_loop(_loop_vec_info*, gimple*)
/home/marxin/Programming/gcc/gcc/tree-vect-loop.c:9095
0x10d070c try_vectorize_loop_1
/home/marxin/Programming/gcc/gcc/tree-vectorizer.c:1089
0x10d1389 vectorize_loops()
/home/marxin/Programming/gcc/gcc/tree-vectorizer.c:1226
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.
next reply other threads:[~2020-10-20 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 7:34 marxin at gcc dot gnu.org [this message]
2020-10-20 7:34 ` [Bug tree-optimization/97500] " marxin at gcc dot gnu.org
2020-10-20 9:46 ` rguenth at gcc dot gnu.org
2020-10-21 9:43 ` cvs-commit at gcc dot gnu.org
2020-10-21 9:43 ` 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-97500-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).