public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103378] [12 Regression] ICE: verify_cgraph_node failed (error: semantic interposition mismatch) since r12-5412-g458d2c689963d846 Date: Thu, 07 Apr 2022 11:34:16 +0000 [thread overview] Message-ID: <bug-103378-4-PcKgW1DmuY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103378-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103378 --- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> --- I am testing diff --git a/gcc/cgraphunit.cc b/gcc/cgraphunit.cc index 01f4e28204e..bc3dc754481 100644 --- a/gcc/cgraphunit.cc +++ b/gcc/cgraphunit.cc @@ -621,6 +621,7 @@ cgraph_node::analyze (void) tree decl = this->decl; location_t saved_loc = input_location; input_location = DECL_SOURCE_LOCATION (decl); + semantic_interposition = opt_for_fn (decl, flag_semantic_interposition); if (thunk) {
next prev parent reply other threads:[~2022-04-07 11:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 10:03 [Bug ipa/103378] New: [12 Regression] ICE: verify_cgraph_node failed (error: semantic interposition mismatch) asolokha at gmx dot com 2021-11-23 10:08 ` [Bug ipa/103378] [12 Regression] ICE: verify_cgraph_node failed (error: semantic interposition mismatch) since r12-5412-g458d2c689963d846 marxin at gcc dot gnu.org 2021-11-23 10:13 ` hubicka at gcc dot gnu.org 2021-11-23 11:38 ` rguenth at gcc dot gnu.org 2021-11-23 16:57 ` hubicka at gcc dot gnu.org 2022-01-18 20:12 ` dcb314 at hotmail dot com 2022-01-19 6:42 ` marxin at gcc dot gnu.org 2022-04-07 11:34 ` hubicka at gcc dot gnu.org [this message] 2022-04-09 20:56 ` hubicka 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-103378-4-PcKgW1DmuY@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).