public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112320] New: crash from insert_debug_temp_for_var_def
Date: Tue, 31 Oct 2023 17:31:01 +0000 [thread overview]
Message-ID: <bug-112320-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112320
Bug ID: 112320
Summary: crash from insert_debug_temp_for_var_def
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
This C code:
unsigned void0_effective_addr2;
void0_i, void0_m, void0_p2;
void0() {
void0_m = 800 - (void0_effective_addr2 & 5);
int b1;
void0_i = 0;
for (; void0_i < void0_m; void0_i++)
b1++;
void0_p2 = b1++;
}
when compiled by recent gcc trunk, does this:
$ ~/gcc/results/bin/gcc -c -w -g -O1 bug972.c
during GIMPLE pass: dse
bug972.c: In function ‘void0’:
bug972.c:3:1: internal compiler error: Segmentation fault
3 | void0() {
| ^~~~~
0xebbce9 crash_signal(int)
../../trunk.year/gcc/toplev.cc:315
0xaa2308 gsi_for_stmt(gimple*)
../../trunk.year/gcc/gimple-iterator.cc:0
0x11364ea insert_debug_temp_for_var_def(gimple_stmt_iterator*, tree_node*)
../../trunk.year/gcc/tree-ssa.cc:471
The bug first seems to occur sometime between g:8c40b72036c967fb
and g:9119b008b4195e06, which is 35 commits.
next reply other threads:[~2023-10-31 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 17:31 dcb314 at hotmail dot com [this message]
2023-10-31 17:35 ` [Bug tree-optimization/112320] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-31 18:37 ` dcb314 at hotmail dot com
2023-10-31 18:47 ` dcb314 at hotmail dot com
2023-10-31 19:46 ` [Bug tree-optimization/112320] [14 Regression] crash from insert_debug_temp_for_var_def since r14-5032-ge3da1d7bb288c8 pinskia at gcc dot gnu.org
2023-10-31 22:21 ` hp at gcc dot gnu.org
2023-11-01 0:39 ` law at gcc dot gnu.org
2023-11-01 0:40 ` law at gcc dot gnu.org
2023-11-01 7:32 ` dcb314 at hotmail dot com
2023-11-01 11:28 ` pinskia at gcc dot gnu.org
2023-11-01 22:45 ` pinskia at gcc dot gnu.org
2023-11-02 8:29 ` rguenth at gcc dot gnu.org
2023-11-02 8:41 ` pinskia at gcc dot gnu.org
2023-11-02 8:42 ` pinskia at gcc dot gnu.org
2023-11-02 10:31 ` cvs-commit at gcc dot gnu.org
2023-11-02 10:31 ` 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-112320-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).