public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/112718] [11/12/13/14 Regression] ICE: in add_dwarf_attr, at dwarf2out.cc:4501 with -g -fdebug-types-section -flto -ffat-lto-objects Date: Mon, 22 Jan 2024 14:46:04 +0000 [thread overview] Message-ID: <bug-112718-4-1I7k0X39yi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112718-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112718 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- I have a patch, but other issues with -fdebug-types-section and -flto will prevail.
next prev parent reply other threads:[~2024-01-22 14:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 6:50 [Bug debug/112718] New: [11/12/13/14 Regression] ICE: in add_dwarf_attr, at dwarf2out.cc:4501 with -g -fdebug-types-section -flto -fno-use-linker-plugin zsojka at seznam dot cz 2023-11-27 8:17 ` [Bug debug/112718] [11/12/13/14 Regression] ICE: in add_dwarf_attr, at dwarf2out.cc:4501 with -g -fdebug-types-section -flto -ffat-lto-objects rguenth at gcc dot gnu.org 2024-01-22 14:46 ` rguenth at gcc dot gnu.org [this message] 2024-01-23 7:06 ` cvs-commit at gcc dot gnu.org 2024-01-23 7:06 ` [Bug debug/112718] [11/12/13 " rguenth at gcc dot gnu.org 2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org 2024-05-17 11:12 ` [Bug debug/112718] [11/12 " cvs-commit at gcc dot gnu.org 2024-06-21 9:22 ` [Bug debug/112718] [11 " cvs-commit at gcc dot gnu.org 2024-06-21 9:36 ` 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-112718-4-1I7k0X39yi@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).