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++/105188] New: ICE in rtl_verify_bb_pointers, at cfgrtl.cc:2829 Date: Wed, 06 Apr 2022 18:28:25 +0000 [thread overview] Message-ID: <bug-105188-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105188 Bug ID: 105188 Summary: ICE in rtl_verify_bb_pointers, at cfgrtl.cc:2829 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Affects versions down to at least r5, at -O1+ : (gcc configured with --enable-checking=yes) $ cat z1.cc typedef struct { char c[0x40000000]; } s; void f (s); int g (s *x) { f (*x); } $ g++-12-20220403 -c z1.cc -O2 z1.cc: In function 'int g(s*)': z1.cc:6:1: warning: no return statement in function returning non-void [-Wreturn-type] 6 | } | ^ z1.cc:5:5: sorry, unimplemented: passing too large argument on stack 5 | f (*x); | ~~^~~~ during RTL pass: expand z1.cc:6:1: internal compiler error: Segmentation fault 6 | } | ^ 0x10d3b0f crash_signal ../../gcc/toplev.cc:322 0xb90233 rtl_verify_bb_pointers ../../gcc/cfgrtl.cc:2829 0xb90233 rtl_verify_flow_info_1 ../../gcc/cfgrtl.cc:2881 0xb90de2 rtl_verify_flow_info ../../gcc/cfgrtl.cc:3126 0xb7028a verify_flow_info() ../../gcc/cfghooks.cc:282 0x1e1e243 checking_verify_flow_info ../../gcc/cfghooks.h:214 0x1e1e243 try_optimize_cfg ../../gcc/cfgcleanup.cc:2980 0x1e1e2e3 cleanup_cfg(int) ../../gcc/cfgcleanup.cc:3143 0xb6d1c6 execute ../../gcc/cfgexpand.cc:6971
next reply other threads:[~2022-04-06 18:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 18:28 gscfq@t-online.de [this message] 2022-04-07 8:07 ` [Bug middle-end/105188] " marxin 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-105188-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).