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 libstdc++/68606] Reduce or disable the static emergency pool for C++ exceptions
Date: Thu, 29 Sep 2022 07:02:26 +0000	[thread overview]
Message-ID: <bug-68606-4-HA8cJ0SxGe@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 #16 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #14)
> (In reply to R. Diez from comment #13)
> > About implementing a proper solution (my patch is just a workaround): There
> > are probably guys who want to control the size of the emergency buffer, but
> > for really constrained environments, I would like an option to disable it
> > completely.
> 
> Yeah, tunable size would be good to do as part of PR 88264, but having a
> build-time configuration to disable it completely is also valuable. And we
> can do that more easily.
> 
> Let's try to do that for GCC 13.

Any such solution would also be OK to backport I think.

  parent reply	other threads:[~2022-09-29  7:02 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
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 [this message]
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-HA8cJ0SxGe@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).