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++/107058] New: [11/12/13 Regression] ICE in dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038
Date: Tue, 27 Sep 2022 16:27:08 +0000	[thread overview]
Message-ID: <bug-107058-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107058
           Summary: [11/12/13 Regression] ICE in
                    dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038
           Product: gcc
           Version: 13.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 g++-11 between 20201108 and 20201115,
using file c-c++-common/pr50459.c :


$ gcc-13-20220925 -c pr50459.c -flto -g -fdebug-types-section
$
$ g++-13-20220925 -c pr50459.c -flto -g -fdebug-types-section
during IPA pass: modref
pr50459.c:13:37: internal compiler error: in dwarf2out_die_ref_for_decl, at
dwarf2out.cc:6038
   13 | int __attribute__((aligned (A))) foo;
      |                                     ^
0xd29259 dwarf2out_die_ref_for_decl
        ../../gcc/dwarf2out.cc:6037
0x1017061 lto_write_tree_1
        ../../gcc/lto-streamer-out.cc:535
0x1017180 lto_write_tree
        ../../gcc/lto-streamer-out.cc:561
0x1017180 lto_output_tree_1
        ../../gcc/lto-streamer-out.cc:592
0x101f425 DFS::DFS(output_block*, tree_node*, bool, bool, bool)
        ../../gcc/lto-streamer-out.cc:892
0x1020bdb lto_output_tree(output_block*, tree_node*, bool, bool)
        ../../gcc/lto-streamer-out.cc:1859
0x1016a02 write_global_stream
        ../../gcc/lto-streamer-out.cc:2853
0x1023cf1 lto_output_decl_state_streams(output_block*, lto_out_decl_state*)
        ../../gcc/lto-streamer-out.cc:2900
0x1023cf1 produce_asm_for_decls()
        ../../gcc/lto-streamer-out.cc:3294
0x10c30bf write_lto
        ../../gcc/passes.cc:2771
0x10c716e ipa_write_summaries_1
        ../../gcc/passes.cc:2832
0x10c716e ipa_write_summaries()
        ../../gcc/passes.cc:2888
0xca8783 ipa_passes
        ../../gcc/cgraphunit.cc:2208
0xca8783 symbol_table::compile()
        ../../gcc/cgraphunit.cc:2281
0xcac42f symbol_table::compile()
        ../../gcc/cgraphunit.cc:2532
0xcac42f symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2529

             reply	other threads:[~2022-09-27 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:27 gscfq@t-online.de [this message]
2022-09-27 16:31 ` [Bug debug/107058] " pinskia at gcc dot gnu.org
2022-09-27 16:42 ` [Bug ipa/107058] " mpolacek at gcc dot gnu.org
2022-09-27 17:24 ` [Bug ipa/107058] [11/12/13 Regression] ICE in dwarf2out_die_ref_for_decl, at dwarf2out.cc:6038 since r11-5003-gd50310408f54e380 marxin at gcc dot gnu.org
2022-09-29  8:05 ` [Bug debug/107058] " rguenth at gcc dot gnu.org
2023-05-29 10:07 ` [Bug debug/107058] [11/12/13/14 " jakub at gcc dot gnu.org
2024-01-23  8:52 ` [Bug c++/107058] " rguenth at gcc dot gnu.org
2024-01-23 10:15 ` cvs-commit at gcc dot gnu.org
2024-01-23 10:16 ` rguenth at gcc dot gnu.org
2024-03-22 14:02 ` law 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-107058-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).