public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdiezmail-gcc at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/68606] Reduce or disable the static emergency pool for C++ exceptions
Date: Wed, 28 Sep 2022 14:01:59 +0000 [thread overview]
Message-ID: <bug-68606-4-hLAsbXnotr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68606-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68606
--- Comment #11 from R. Diez <rdiezmail-gcc at yahoo dot de> ---
> Has a solution been found for embedded systems with very limited resources?
> In this case for example, C++ exceptions can be disabled and this
> emergency pool not needed.
Contrary to popular belief, C++ exception handling does not need many
resources. I have been generating dynamic error messages in readable English
using C++ exceptions on microcontrollers with as little as 16 KiB SRAM for
years, with 'plenty' of memory to spare.
To that effect, I have been using the patch that I mentioned above. Here is an
updated URL for it:
https://github.com/rdiez/JtagDue/blob/master/Toolchain/Patches/GccDisableCppExceptionEmergencyBuffer-GCC-5.3.0.patch
next prev parent reply other threads:[~2022-09-28 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-68606-4@http.gcc.gnu.org/bugzilla/>
2020-05-23 15:45 ` egallager at gcc dot gnu.org
2022-09-28 7:00 ` dumoulin.thibaut at gmail dot com
2022-09-28 14:01 ` rdiezmail-gcc at yahoo dot de [this message]
2022-09-28 14:42 ` dumoulin.thibaut at gmail dot com
2022-09-28 15:14 ` rdiezmail-gcc at yahoo dot de
2022-09-28 20:20 ` redi at gcc dot gnu.org
2022-09-28 20:24 ` redi at gcc dot gnu.org
2022-09-29 7:02 ` rguenth at gcc dot gnu.org
2022-09-29 9:31 ` redi at gcc dot gnu.org
2022-09-29 12:24 ` dumoulin.thibaut at gmail dot com
2022-09-29 13:01 ` redi at gcc dot gnu.org
2022-10-07 15:55 ` redi at gcc dot gnu.org
2022-10-11 15:22 ` cvs-commit at gcc dot gnu.org
2022-10-11 15:25 ` redi 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-68606-4-hLAsbXnotr@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: link
Be 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).