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 target/106861] ICE in add_cfi_args_size, at dwarf2cfi.cc:501 Date: Wed, 19 Oct 2022 06:05:39 +0000 [thread overview] Message-ID: <bug-106861-4-OrGIrKtcvR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106861-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106861 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[12/13 Regression] ICE in |ICE in add_cfi_args_size, |add_cfi_args_size, at |at dwarf2cfi.cc:501 |dwarf2cfi.cc:501 | Target Milestone|12.3 |--- --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- So it's not a regression, with GCC 12+ -fnon-call-exceptions adds -fexceptions implicitely.
prev parent reply other threads:[~2022-10-19 6:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:19 [Bug c/106861] New: [12/13 Regression] " gscfq@t-online.de 2022-09-07 8:49 ` [Bug target/106861] " rguenth at gcc dot gnu.org 2022-09-07 12:09 ` marxin at gcc dot gnu.org 2022-10-19 6:05 ` rguenth at gcc dot gnu.org [this message]
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-106861-4-OrGIrKtcvR@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).