public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106859] New: [10/11/12/13 Regression] ICE in val_store, at var-tracking.cc:2532 Date: Tue, 06 Sep 2022 17:16:38 +0000 [thread overview] Message-ID: <bug-106859-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106859 Bug ID: 106859 Summary: [10/11/12/13 Regression] ICE in val_store, at var-tracking.cc:2532 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r7 at -O1+ and with file gcc.dg/torture/pr90553.c : $ gcc-13-20220904 -c pr90553.c -O2 -da -funroll-loops -fcompare-debug during RTL pass: vartrack dump file: pr90553.gk.c.328r.vartrack pr90553.c: In function 'f2': pr90553.c:58:1: internal compiler error: Segmentation fault 58 | } | ^ 0xec93cf crash_signal ../../gcc/toplev.cc:314 0x127cc04 INSN_UID(rtx_def*) ../../gcc/rtl.h:1453 0x127cc04 val_store ../../gcc/var-tracking.cc:2532 0x127d826 compute_bb_dataflow ../../gcc/var-tracking.cc:6961 0x127e658 vt_find_locations ../../gcc/var-tracking.cc:7200 0x127fef3 variable_tracking_main_1 ../../gcc/var-tracking.cc:10519 0x127fef3 variable_tracking_main() ../../gcc/var-tracking.cc:10565 0x127fef3 execute ../../gcc/var-tracking.cc:10602
next reply other threads:[~2022-09-06 17:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:16 gscfq@t-online.de [this message] 2022-09-07 8:27 ` [Bug debug/106859] " rguenth at gcc dot gnu.org 2022-09-07 12:07 ` [Bug debug/106859] [10/11/12/13 Regression] ICE in val_store, at var-tracking.cc:2532 since r7-3839-gde0a3fa38e2ad8f3 marxin at gcc dot gnu.org 2022-10-19 6:06 ` rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug debug/106859] [11/12/13/14 " 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-106859-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: linkBe 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).