public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106421] New: ICE with computed goto from a nested functon Date: Sat, 23 Jul 2022 10:58:53 +0000 [thread overview] Message-ID: <bug-106421-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106421 Bug ID: 106421 Summary: ICE with computed goto from a nested functon Product: gcc Version: unknown Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: amonakov at gcc dot gnu.org Target Milestone: --- int main(int argc, char **argv) { __label__ loop, end; void jmp(int c) { goto *(c ? &&loop : &&end); } loop: jmp(argc < 0); end:{} } makes gcc -O2 segfault in find_edge during RTL cprop. The documentation might want to specify that goto from a nested function to a containing function cannot be a 'computed goto' (must refer to the target label directly by name).
next reply other threads:[~2022-07-23 10:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-23 10:58 amonakov at gcc dot gnu.org [this message] 2022-07-24 20:19 ` [Bug middle-end/106421] " pinskia at gcc dot gnu.org 2022-07-24 20:22 ` [Bug rtl-optimization/106421] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-24 20:23 ` pinskia at gcc dot gnu.org 2022-07-25 7:07 ` marxin at gcc dot gnu.org 2022-07-25 9:27 ` rguenth at gcc dot gnu.org 2022-07-25 14:57 ` rguenth at gcc dot gnu.org 2023-01-10 14:07 ` cvs-commit at gcc dot gnu.org 2023-04-27 13:19 ` [Bug rtl-optimization/106421] [10/11/12 " cvs-commit at gcc dot gnu.org 2023-07-07 10:43 ` [Bug rtl-optimization/106421] [11 " 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-106421-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).