public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/108962] New: d: Don't generate code that throws exceptions when compiling with `-fno-exceptions' Date: Tue, 28 Feb 2023 06:06:17 +0000 [thread overview] Message-ID: <bug-108962-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108962 Bug ID: 108962 Summary: d: Don't generate code that throws exceptions when compiling with `-fno-exceptions' Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ibuclaw at gcc dot gnu.org Target Milestone: --- There are a few constructs that implicitly raise an Error exception, for example, `final switch`. ``` void main() { final switch (0) { case 1: return; } } ``` It might be more desirable to instead abort the runtime, optionally creating a trace before exiting.
next reply other threads:[~2023-02-28 6:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 6:06 ibuclaw at gcc dot gnu.org [this message] 2023-07-02 13:54 ` [Bug d/108962] " cvs-commit at gcc dot gnu.org 2023-07-02 13:55 ` cvs-commit at gcc dot gnu.org 2023-07-02 13:56 ` ibuclaw 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-108962-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: 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).