public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dumoulin.thibaut at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64535] Emergency buffer for exception allocation too small
Date: Tue, 27 Sep 2022 15:45:43 +0000	[thread overview]
Message-ID: <bug-64535-4-mQ5rYoGcWd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64535-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64535

Thibaut M. <dumoulin.thibaut at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dumoulin.thibaut at gmail dot com

--- Comment #27 from Thibaut M. <dumoulin.thibaut at gmail dot com> ---
With this patch, a global variable is declared and `malloc` is called in its
constructor.

Linking libstdc++ will automatically allocate at least 2528 bytes on the heap.
Since this library is also used in embedded software, this is a problem, 2,5ko
represent a lot of memory (when you have only 4ko available for example). A
temporary solution would be to call the freeres() function but better solution
would be to do not allocate at all.

Second problem with this commit: the constructor of the global variable `pool
emergency_pool` must be call at run time due to `malloc` and `new` functions.
Even if this code is not used, the linker script will put the constructor in
`.init_array` section. Linker cannot get rid of this constructor due to
non-pure functions called.

A patch could be a least to avoid this `malloc` with some `#define` options?

Or maybe you know a solution to avoid those problems?

  parent reply	other threads:[~2022-09-27 15:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  9:43 [Bug libstdc++/64535] New: " rguenth at gcc dot gnu.org
2015-01-08 11:11 ` [Bug libstdc++/64535] " rguenth at gcc dot gnu.org
2015-01-08 11:27 ` rguenth at gcc dot gnu.org
2015-01-08 11:39 ` rguenth at gcc dot gnu.org
2015-01-08 11:57 ` rguenth at gcc dot gnu.org
2015-01-08 12:48 ` rguenth at gcc dot gnu.org
2015-01-09  8:44 ` jakub at gcc dot gnu.org
2015-01-09  9:01 ` rguenth at gcc dot gnu.org
2015-01-12 10:03 ` rguenth at gcc dot gnu.org
2015-01-12 10:19 ` rguenther at suse dot de
2015-01-12 14:11 ` rguenth at gcc dot gnu.org
2015-01-21 11:18 ` redi at gcc dot gnu.org
2015-01-22  9:22 ` rguenth at gcc dot gnu.org
2015-01-22  9:56 ` rguenth at gcc dot gnu.org
2015-01-26 22:36 ` redi at gcc dot gnu.org
2015-01-27 11:15 ` rguenth at gcc dot gnu.org
2015-01-27 11:22 ` redi at gcc dot gnu.org
2015-01-27 11:49 ` rguenther at suse dot de
2015-01-27 11:55 ` jakub at gcc dot gnu.org
2015-01-27 12:10 ` rguenther at suse dot de
2015-01-27 12:23 ` rguenth at gcc dot gnu.org
2015-01-27 12:30 ` jakub at gcc dot gnu.org
2015-01-27 12:34 ` rguenther at suse dot de
2015-01-27 12:39 ` jakub at gcc dot gnu.org
2015-01-27 12:45 ` redi at gcc dot gnu.org
2015-01-27 12:55 ` rguenther at suse dot de
2022-09-27 15:45 ` dumoulin.thibaut at gmail dot com [this message]
2022-09-27 16:05 ` 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-64535-4-mQ5rYoGcWd@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).