public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/106061] [13 Regression] during GIMPLE pass: einline ICE: verify_cgraph_node failed (edge points to wrong declaration) with -Og since r13-1204-gd68d366425369649 Date: Fri, 11 Nov 2022 18:06:51 +0000 [thread overview] Message-ID: <bug-106061-4-rKsKXsUOcu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106061-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106061 Yann Droneaud <yann at droneaud dot fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yann at droneaud dot fr --- Comment #6 from Yann Droneaud <yann at droneaud dot fr> --- I'm reaching this bug too, compiling the following smaller reproducer: extern void a(void); inline void b(int c) { if (c) a(); } void d(void) { b(0); }
next prev parent reply other threads:[~2022-11-11 18:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 4:46 [Bug ipa/106061] New: [13 Regression] during GIMPLE pass: einline ICE: verify_cgraph_node failed (edge points to wrong declaration) with -Og zsojka at seznam dot cz 2022-06-23 6:47 ` [Bug ipa/106061] [13 Regression] during GIMPLE pass: einline ICE: verify_cgraph_node failed (edge points to wrong declaration) with -Og since r13-1204-gd68d366425369649 marxin at gcc dot gnu.org 2022-06-24 10:09 ` rguenth at gcc dot gnu.org 2022-07-14 17:27 ` pinskia at gcc dot gnu.org 2022-08-10 19:25 ` pinskia at gcc dot gnu.org 2022-10-11 23:20 ` pinskia at gcc dot gnu.org 2022-10-11 23:23 ` pinskia at gcc dot gnu.org 2022-11-11 18:06 ` yann at droneaud dot fr [this message] 2022-12-20 14:37 ` rguenth at gcc dot gnu.org 2023-01-27 10:17 ` cvs-commit at gcc dot gnu.org 2023-01-27 10:18 ` jakub 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-106061-4-rKsKXsUOcu@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).