public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103378] New: [12 Regression] ICE: verify_cgraph_node failed (error: semantic interposition mismatch)
Date: Tue, 23 Nov 2021 10:03:27 +0000	[thread overview]
Message-ID: <bug-103378-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103378

            Bug ID: 103378
           Summary: [12 Regression] ICE: verify_cgraph_node failed (error:
                    semantic interposition mismatch)
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

gcc-12.0.0-alpha20211121 snapshot (g:da17c304e22ba256eba0b03710aa329115163b08)
ICEs when compiling the following testcase, extracted from
gcc/testsuite/c-c++-common/attr-opt-1.c, w/ -Ofast:

__attribute__ ((optimize ("no-associative-math"))) double
fn3 (double h, double l)
{
  return h + l;
}

double fn3 (double, double) __attribute__ ((optimize
("O2,no-associative-math")));

% gcc-12.0.0 -Ofast -w -c rtonutgr.c
rtonutgr.c:7:1: error: semantic interposition mismatch
    7 | double fn3 (double, double) __attribute__ ((optimize
("O2,no-associative-math")));
      | ^~~~~~
fn3/0 (fn3) @0x7f290eed1220
  Type: function definition analyzed
  Visibility: externally_visible public
  References:
  Referring:
  Availability: available
  Function flags: body
  Called by:
  Calls:
during IPA pass: visibility
rtonutgr.c:7:1: internal compiler error: verify_cgraph_node failed
0x9fc620 cgraph_node::verify_node()
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/cgraph.c:3873
0x9eb854 symtab_node::verify()
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/symtab.c:1358
0x9eca37 symtab_node::verify_symtab_nodes()
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/symtab.c:1386
0xca49a4 symtab_node::checking_verify_symtab_nodes()
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/cgraph.h:682
0xca49a4 symbol_table::remove_unreachable_nodes(_IO_FILE*)
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/ipa.c:679
0xdb9289 execute_todo
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211121/work/gcc-12-20211121/gcc/passes.c:2110

             reply	other threads:[~2021-11-23 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 10:03 asolokha at gmx dot com [this message]
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
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@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: link
Be 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).