public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/105551] New: [nvptx] ICE in final_scan_insn_1, at final.cc:2629 when building libgcc2.c since r13-259-g76db543db88727789a6c117608a23edc2eace713
Date: Tue, 10 May 2022 15:36:06 +0000 [thread overview]
Message-ID: <bug-105551-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105551
Bug ID: 105551
Summary: [nvptx] ICE in final_scan_insn_1, at final.cc:2629
when building libgcc2.c since
r13-259-g76db543db88727789a6c117608a23edc2eace713
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: build, ice-on-valid-code
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org, tschwinge at gcc dot gnu.org,
vries at gcc dot gnu.org
Target Milestone: ---
Target: nvptx-none
..../gcc/xgcc \
-B.../gcc/ -B.../nvptx-none/bin/ -B.../nvptx-none/lib/ -isystem
.../nvptx-none/include -isystem .../nvptx-none/sys-include
--sysroot=.../nvptx-none -g -O2 -mgomp -O2 -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -Dinhibit_libc -I. -I. -I../../.././gcc
-I.../src/gcc-mainline/libgcc -I.../src/gcc-mainline/libgcc/.
-I.../src/gcc-mainline/libgcc/../gcc -I.../src/gcc-mainline/libgcc/../include
-DHAVE_CC_TLS -DUSE_EMUTLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep
-DL_muldi3 -c .../src/gcc-mainline/libgcc/libgcc2.c
during RTL pass: final
.../src/gcc-mainline/libgcc/libgcc2.c: In function '__multi3':
.../src/gcc-mainline/libgcc/libgcc2.c:538:1: internal compiler error: in
final_scan_insn_1, at final.cc:2629
538 | }
| ^
0x9a6288 final_scan_insn_1
.../src/gcc-mainline/gcc/final.cc:2629
0x9a642b final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
.../src/gcc-mainline/gcc/final.cc:2940
0x9a6545 final_1
.../src/gcc-mainline/gcc/final.cc:1997
0x9a7564 rest_of_handle_final
.../src/gcc-mainline/gcc/final.cc:4285
0x9a7564 execute
.../src/gcc-mainline/gcc/final.cc:4363
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Bisecting points to r13-259-g76db543db88727789a6c117608a23edc2eace713
commit 76db543db88727789a6c117608a23edc2eace713
Author: Richard Biener <rguenther@suse.de>
Date: Tue May 10 11:44:40 2022 +0200
middle-end/105537 - debug processing
The following makes sure to have a consistent state of
flag_var_tracking_assignments with the distributed handling
in process_options and finish_options by moving everything to
finish_options which also restores diagnostics for
-g0 -fvar-tracking which was lost with previous changes.
2022-05-10 Richard Biener <rguenther@suse.de>
PR middle-end/105537
* toplev.cc (process_options): Move flag_var_tracking
handling ...
* opts.cc (finish_options): ... here.
* gcc.dg/torture/pr105537.c: New testcase.
next reply other threads:[~2022-05-10 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:36 burnus at gcc dot gnu.org [this message]
2022-05-10 15:39 ` [Bug bootstrap/105551] [13 Regression] " burnus at gcc dot gnu.org
2022-05-11 6:35 ` rguenther at suse dot de
2022-05-11 6:56 ` rguenth at gcc dot gnu.org
2022-05-11 7:03 ` rguenth at gcc dot gnu.org
2022-05-11 8:32 ` burnus at gcc dot gnu.org
2022-05-11 8:50 ` cvs-commit at gcc dot gnu.org
2022-05-11 8:50 ` rguenth at gcc dot gnu.org
2022-06-29 9:39 ` cvs-commit 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-105551-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).