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++/104648] New: [12 Regression] ICE in cgraphunit_cc_finalize,  at cgraphunit.cc:2540
Date: Tue, 22 Feb 2022 19:33:19 +0000	[thread overview]
Message-ID: <bug-104648-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104648
           Summary: [12 Regression] ICE in cgraphunit_cc_finalize, at
                    cgraphunit.cc:2540
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r12 :
(gcc configured with --enable-checking=yes)


$ cat z1.cc
struct A {};
struct B : virtual A
{
  B () {};
  B () {};
};


$ g++-12-20220220 -c z1.cc -fvtable-verify=preinit
z1.cc:5:3: error: 'B::B()' cannot be overloaded with 'B::B()'
    5 |   B () {};
      |   ^
z1.cc:4:3: note: previous declaration 'B::B()'
    4 |   B () {};
      |   ^
internal compiler error: in cgraphunit_cc_finalize, at cgraphunit.cc:2540
0x10cbf86 toplev::finalize()
        ../../gcc/toplev.cc:2365
g++: internal compiler error: Segmentation fault signal terminated program
cc1plus

             reply	other threads:[~2022-02-22 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 19:33 gscfq@t-online.de [this message]
2022-02-23  8:31 ` [Bug ipa/104648] " rguenth at gcc dot gnu.org
2022-02-24 10:23 ` marxin at gcc dot gnu.org
2022-02-28 13:02 ` cvs-commit at gcc dot gnu.org
2022-02-28 13:02 ` marxin 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-104648-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).