public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/99421] New: ICE:in code_motion_process_successors, at sel-sched.c:6389 on aarch64
Date: Fri, 05 Mar 2021 20:31:47 +0000 [thread overview]
Message-ID: <bug-99421-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99421
Bug ID: 99421
Summary: ICE:in code_motion_process_successors, at
sel-sched.c:6389 on aarch64
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: qinzhao at gcc dot gnu.org
Target Milestone: ---
with the attached tar file, (from CPU2017 502.gcc_r)
untar it,
cd bug_3
sh t
during RTL pass: sched2
predict.c: In function ‘expr_expected_value_1’:
predict.c:1263:1: internal compiler error: in code_motion_process_successors,
at sel-sched.c:6389
0xd83883 code_motion_process_successors
../../latest_gcc_2/gcc/sel-sched.c:6386
0xd83883 code_motion_path_driver
../../latest_gcc_2/gcc/sel-sched.c:6609
0xd834f7 code_motion_process_successors
../../latest_gcc_2/gcc/sel-sched.c:6343
0xd834f7 code_motion_path_driver
../../latest_gcc_2/gcc/sel-sched.c:6609
0xd8645f move_op
../../latest_gcc_2/gcc/sel-sched.c:6702
0xd8645f move_exprs_to_boundary
../../latest_gcc_2/gcc/sel-sched.c:5224
0xd8645f schedule_expr_on_boundary
../../latest_gcc_2/gcc/sel-sched.c:5436
0xd87be3 fill_insns
../../latest_gcc_2/gcc/sel-sched.c:5578
0xd8a143 schedule_on_fences
../../latest_gcc_2/gcc/sel-sched.c:7353
0xd8a143 sel_sched_region_2
../../latest_gcc_2/gcc/sel-sched.c:7491
0xd8ac43 sel_sched_region_1
../../latest_gcc_2/gcc/sel-sched.c:7533
0xd8cc83 sel_sched_region(int)
../../latest_gcc_2/gcc/sel-sched.c:7634
0xd8d8d7 run_selective_scheduling()
../../latest_gcc_2/gcc/sel-sched.c:7720
0xd68977 rest_of_handle_sched2
../../latest_gcc_2/gcc/sched-rgn.c:3738
0xd68977 execute
../../latest_gcc_2/gcc/sched-rgn.c:3882
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.
NOTE, this error is repeated with -fprofile-use, and the pre-generated
profiling data file predict.gcda is generated with gcc11 as following:
Target: aarch64-unknown-linux-gnu
Configured with: ../latest_gcc_2/configure
--prefix=/home/qinzhao/Install/latest-2 --enable-languages=c,c++,fortran,lto
--disable-bootstrap
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.0.1 20210304 (experimental) (GCC)
since the error depends on the profiling feedback data, the testing case cannot
be reduced by hand or by tool (Creduce), I have to attach the complete
preprocessed file to repeat the error.
next reply other threads:[~2021-03-05 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 20:31 qinzhao at gcc dot gnu.org [this message]
2021-03-06 8:30 ` [Bug rtl-optimization/99421] " marxin at gcc dot gnu.org
2021-03-06 16:33 ` qinzhao at gcc dot gnu.org
2021-03-08 8:16 ` marxin at gcc dot gnu.org
2021-03-08 8:16 ` marxin at gcc dot gnu.org
2021-03-08 15:39 ` qinzhao at gcc dot gnu.org
2021-03-08 17:58 ` marxin at gcc dot gnu.org
2021-03-09 9:49 ` marxin at gcc dot gnu.org
2021-03-09 9:50 ` marxin at gcc dot gnu.org
2021-03-09 16:39 ` qing.zhao at oracle dot com
2021-03-09 17:12 ` marxin 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-99421-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).