public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/88264] Support glibc-style tunables for libstdc++ Date: Tue, 05 Dec 2023 14:30:32 +0000 [thread overview] Message-ID: <bug-88264-4-d0JmZzAhH4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88264 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- Another tunable idea: disable exceptions from the runtime. We use _GLIBCXX_THROW_OR_ABORT so that throwing an exception will abort instead when -fno-exceptions is defined. However, this only works when the code doing the throw is compiled with that flag. For all the __throw_foo_error functions declared in <bits/functexcept.h> the actual definition is src/c++11/functexcept.cc which isn't affected by any -fno-exceptions that users compile with. You need to recompile libstdc++ itself with -fno-exceptions. We could add a tunable to disable all exceptions within the runtime. (If doing this, don't forget places like throw_revursive_init_exception in libsupc++/guard.cc which doesn't use _GLIBCXX_THROW_OR_ABORT because it wants to trap not std::abort(), presumably for freestanding reasons.)
prev parent reply other threads:[~2023-12-05 14:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88264-4@http.gcc.gnu.org/bugzilla/> 2022-10-11 15:22 ` [Bug libstdc++/88264] Support glibc-style tunables for <memory_resource> cvs-commit at gcc dot gnu.org 2022-10-11 15:26 ` redi at gcc dot gnu.org 2022-11-21 12:44 ` redi at gcc dot gnu.org 2023-12-05 14:30 ` redi 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-88264-4-d0JmZzAhH4@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).