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++/108684] New: [13 Regression] ICE: verify_ssa failed Date: Mon, 06 Feb 2023 18:49:49 +0000 [thread overview] Message-ID: <bug-108684-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684 Bug ID: 108684 Summary: [13 Regression] ICE: verify_ssa failed Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20221030 and 20221106 : (gcc configured with --enable-checking=yes) $ cat z1.cc int f (int a) { asm (" " : "=r" (a) : : "eax", "memory"); if (a) return 0; } $ gcc-13-20230205 -c z1.cc -O2 z1.cc: In function 'int f(int)': z1.cc:6:1: warning: control reaches end of non-void function [-Wreturn-type] 6 | } | ^ z1.cc:1:5: error: virtual use of statement not up to date 1 | int f (int a) | ^ # VUSE <_2> return 0; during GIMPLE pass: vrp z1.cc:1:5: internal compiler error: verify_ssa failed 0x14e901b verify_ssa(bool, bool) ../../gcc/tree-ssa.cc:1211 0x1134857 execute_function_todo ../../gcc/passes.cc:2098 0x11351a2 execute_todo ../../gcc/passes.cc:2145
next reply other threads:[~2023-02-06 18:49 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-06 18:49 gscfq@t-online.de [this message] 2023-02-06 18:55 ` [Bug tree-optimization/108684] " pinskia at gcc dot gnu.org 2023-02-06 20:23 ` pinskia at gcc dot gnu.org 2023-02-06 20:26 ` pinskia at gcc dot gnu.org 2023-02-07 14:05 ` rguenth at gcc dot gnu.org 2023-02-07 18:30 ` amacleod at redhat dot com 2023-02-07 18:33 ` pinskia at gcc dot gnu.org 2023-02-07 18:37 ` [Bug tree-optimization/108684] [12/13 " pinskia at gcc dot gnu.org 2023-02-07 18:39 ` amacleod at redhat dot com 2023-02-07 18:45 ` pinskia at gcc dot gnu.org 2023-02-07 19:56 ` pinskia at gcc dot gnu.org 2023-02-07 19:59 ` jakub at gcc dot gnu.org 2023-02-07 20:03 ` pinskia at gcc dot gnu.org 2023-02-08 19:14 ` pinskia at gcc dot gnu.org 2023-02-09 15:23 ` pinskia at gcc dot gnu.org 2023-02-10 1:47 ` cvs-commit at gcc dot gnu.org 2023-02-10 1:48 ` [Bug tree-optimization/108684] [12 " pinskia at gcc dot gnu.org 2023-03-10 21:55 ` cvs-commit at gcc dot gnu.org 2023-03-10 21:55 ` pinskia at gcc dot gnu.org 2023-05-13 14:17 ` pinskia 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-108684-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).