public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/105459] New: ICE: Segmentation fault (in record_operand_costs) Date: Tue, 03 May 2022 05:24:38 +0000 [thread overview] Message-ID: <bug-105459-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105459 Bug ID: 105459 Summary: ICE: Segmentation fault (in record_operand_costs) Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gcc 12.0.1 20220424 snapshot (g:6b7441a46c771aa6ecdc0c8ed96197417d036b9a) ICEs when compiling the following testcase w/ -O1 -flto: double m; int n; __attribute__ ((optimize ("-funsafe-math-optimizations"))) void bar (int x) { n = x; m = n; } __attribute__ ((flatten)) void foo (int x) { bar (x); } void quux (void) { ++n; } int main (void) { foo (0); quux (); return 0; } % x86_64-unknown-linux-gnu-gcc-12.0.1 -O1 -flto qnipdldf.c during RTL pass: ira qnipdldf.c: In function 'main': qnipdldf.c:30:1: internal compiler error: Segmentation fault 30 | } | ^ 0xd95abf crash_signal /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/toplev.cc:322 0xbabeb8 record_operand_costs /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-costs.cc:1382 0xbac464 scan_one_insn /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-costs.cc:1507 0xbac464 process_bb_for_costs /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-costs.cc:1632 0xba2ae1 ira_traverse_loop_tree(bool, ira_loop_tree_node*, void (*)(ira_loop_tree_node*), void (*)(ira_loop_tree_node*)) /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-build.cc:1800 0xbad545 find_costs_and_classes /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-costs.cc:1728 0xbae639 ira_costs() /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-costs.cc:2276 0xba806c ira_build() /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira-build.cc:3481 0xb9dd0c ira /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira.cc:5760 0xb9dd0c execute /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/ira.cc:6083 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. lto-wrapper: fatal error: x86_64-unknown-linux-gnu-gcc-12.0.1 returned 1 exit status compilation terminated. /usr/lib/gcc/x86_64-unknown-linux-gnu/12.0.1/../../../../x86_64-unknown-linux-gnu/bin/ld: fatal error: lto-wrapper failed
next reply other threads:[~2022-05-03 5:24 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 5:24 asolokha at gmx dot com [this message] 2022-05-03 7:07 ` [Bug rtl-optimization/105459] " rguenth at gcc dot gnu.org 2022-05-03 8:46 ` [Bug rtl-optimization/105459] [12/13 Regression] ICE: Segmentation fault (in record_operand_costs) since r12-3721-g63c6446f77b9001d marxin at gcc dot gnu.org 2022-05-03 8:47 ` marxin at gcc dot gnu.org 2022-05-03 9:00 ` rguenth at gcc dot gnu.org 2022-05-05 5:45 ` linkw at gcc dot gnu.org 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-17 9:08 ` linkw at gcc dot gnu.org 2022-05-17 9:10 ` linkw at gcc dot gnu.org 2022-05-23 6:28 ` linkw at gcc dot gnu.org 2022-05-23 8:14 ` linkw at gcc dot gnu.org 2022-05-25 7:43 ` linkw at gcc dot gnu.org 2022-06-02 2:15 ` linkw at gcc dot gnu.org 2022-06-02 2:18 ` linkw at gcc dot gnu.org 2022-07-11 9:22 ` cvs-commit at gcc dot gnu.org 2022-07-11 9:22 ` [Bug rtl-optimization/105459] [12 " rguenth at gcc dot gnu.org 2022-07-19 11:37 ` cvs-commit at gcc dot gnu.org 2022-07-19 11:38 ` 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-105459-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).