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/106913] New: [13 Regression] ICE in dump_bb_info, at cfg.cc:796 Date: Mon, 12 Sep 2022 17:25:39 +0000 [thread overview] Message-ID: <bug-106913-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106913 Bug ID: 106913 Summary: [13 Regression] ICE in dump_bb_info, at cfg.cc:796 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 between 20220828 and 20220904, at -O0, with file gcc.dg/pr51879.c (and several others) : $ cat z1.c # alias pr51879.c int bar (int); void baz (int); void foo (int y) { int a; if (y == 6) a = bar (7); else a = bar (7); baz (a); } $ gcc-13-20220911 -c z1.c -O0 -da -Wall during RTL pass: jump dump file: z1.c.257r.jump z1.c: In function 'foo': z1.c:12:1: internal compiler error: in dump_bb_info, at cfg.cc:796 12 | } | ^ 0x9433ec dump_bb_info(_IO_FILE*, basic_block_def*, int, dump_flag, bool, bool) ../../gcc/cfg.cc:796 0x965f97 dump_bb(_IO_FILE*, basic_block_def*, int, dump_flag) ../../gcc/cfghooks.cc:299 0x9661cf dump_flow_info(_IO_FILE*, dump_flag) ../../gcc/cfghooks.cc:361 0x1c019cd execute ../../gcc/cfgcleanup.cc:3239
next reply other threads:[~2022-09-12 17:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 17:25 gscfq@t-online.de [this message] 2022-09-12 19:37 ` [Bug rtl-optimization/106913] [13 Regression] ICE in dump_bb_info, at cfg.cc:796 since r13-2263-gf71abacfed170852 marxin at gcc dot gnu.org 2022-09-13 6:45 ` rguenth at gcc dot gnu.org 2022-09-13 8:52 ` cvs-commit at gcc dot gnu.org 2022-09-13 8:53 ` 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-106913-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).