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 middle-end/112710] [13/14 Regression] ICE: in write_type, at cp/mangle.cc:2226 with -fdump-go-spec=filename -flto -fno-use-linker-plugin Date: Mon, 27 Nov 2023 08:06:09 +0000 [thread overview] Message-ID: <bug-112710-4-NtvBlSXyjq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112710-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112710 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.3 CC| |iant at google dot com --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I'm not sure whether you are supposed to do -fdump-go-spec=... with -flto (LTO scraps some FE specific data).
next prev parent reply other threads:[~2023-11-27 8:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-25 11:36 [Bug middle-end/112710] New: " zsojka at seznam dot cz 2023-11-27 8:06 ` rguenth at gcc dot gnu.org [this message] 2023-11-27 23:59 ` [Bug middle-end/112710] " ian at airs dot com 2023-11-28 6:13 ` zsojka at seznam dot cz 2024-03-15 15:28 ` law at gcc dot gnu.org 2024-05-21 9:18 ` [Bug middle-end/112710] [13/14/15 " jakub 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-112710-4-NtvBlSXyjq@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).