public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94273] New: ice in splice_child_die, at dwarf2out.c:5657
Date: Mon, 23 Mar 2020 11:20:25 +0000	[thread overview]
Message-ID: <bug-94273-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94273
           Summary: ice in splice_child_die, at dwarf2out.c:5657
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 48085
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48085&action=edit
gzipped C++ source code

For the attached C++ source code, with recent gcc trunk, does this:

../tdutils/td/utils/logging.cpp:263:1: internal compiler error: in
splice_child_die, at dwarf2out.c:5657
  263 | }  // namespace td
      | ^
0x7064f4 splice_child_die
    ../../trunk.git/gcc/dwarf2out.c:5657
0x7064f4 gen_member_die
    ../../trunk.git/gcc/dwarf2out.c:25154
0x7064f4 gen_struct_or_union_type_die
    ../../trunk.git/gcc/dwarf2out.c:25265
0x7064f4 gen_tagged_type_die
    ../../trunk.git/gcc/dwarf2out.c:25466

Compile line needs flag -g1.

I'll have my usual go at reducing the code and finding a set of dates
where it first starts to go wrong.

             reply	other threads:[~2020-03-23 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 11:20 dcb314 at hotmail dot com [this message]
2020-03-23 11:28 ` [Bug c++/94273] " dcb314 at hotmail dot com
2020-03-23 11:41 ` dcb314 at hotmail dot com
2020-03-23 12:55 ` [Bug debug/94273] [10 Regression] ICE in splice_child_die, at dwarf2out.c:5657 since r10-7235-g52b3aa8be1893848 marxin at gcc dot gnu.org
2020-03-23 12:55 ` marxin at gcc dot gnu.org
2020-03-23 14:08 ` rguenth at gcc dot gnu.org
2020-03-23 19:53 ` stilor at att dot net
2020-03-26 13:12 ` jakub at gcc dot gnu.org
2020-03-26 13:21 ` rguenth at gcc dot gnu.org
2020-03-26 19:01 ` stilor at att dot net
2020-03-26 23:39 ` stilor at att dot net
2020-03-27  8:37 ` rguenth at gcc dot gnu.org
2020-03-27  8:46 ` rguenth at gcc dot gnu.org
2020-03-27 13:01 ` cvs-commit at gcc dot gnu.org
2020-03-27 13:01 ` rguenth 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-94273-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).