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/105952] New: [12/13 Regression] ICE in sel_redirect_edge_and_branch, at sel-sched-ir.cc:5680 Date: Mon, 13 Jun 2022 17:46:25 +0000 [thread overview] Message-ID: <bug-105952-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105952 Bug ID: 105952 Summary: [12/13 Regression] ICE in sel_redirect_edge_and_branch, at sel-sched-ir.cc:5680 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 20220306 and 20220327, affects file pr27531-1.c : (gcc configured with --enable-checking=yes) $ gcc-13-20220612 -c pr27531-1.c -O -fno-inline -fschedule-insns -fselective-scheduling during RTL pass: sched1 pr27531-1.c: In function 'main': pr27531-1.c:59:1: internal compiler error: Segmentation fault 59 | } | ^ 0xe13ecf crash_signal ../../gcc/toplev.cc:322 0xdbd165 sel_redirect_edge_and_branch(edge_def*, basic_block_def*) ../../gcc/sel-sched-ir.cc:5680 0xdbe0a8 maybe_tidy_empty_bb ../../gcc/sel-sched-ir.cc:3804 0xdbec65 purge_empty_blocks() ../../gcc/sel-sched-ir.cc:3948 0xdd1b4c sel_sched_region_1 ../../gcc/sel-sched.cc:7519 0xdd2ff0 sel_sched_region(int) ../../gcc/sel-sched.cc:7634 0xdd3899 run_selective_scheduling() ../../gcc/sel-sched.cc:7720 0xdafa1d rest_of_handle_sched ../../gcc/sched-rgn.cc:3720 0xdafa1d execute ../../gcc/sched-rgn.cc:3830
next reply other threads:[~2022-06-13 17:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 17:46 gscfq@t-online.de [this message] 2022-06-14 8:19 ` [Bug rtl-optimization/105952] " rguenth at gcc dot gnu.org 2022-06-16 13:47 ` marxin at gcc dot gnu.org 2022-07-25 16:02 ` rguenth at gcc dot gnu.org 2023-05-08 12:24 ` [Bug rtl-optimization/105952] [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-105952-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).