From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BA4BF3857BB1; Wed, 28 Sep 2022 07:00:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BA4BF3857BB1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664348452; bh=aJM13smWbxYwaGbfLDNh4/IPdXJAltQRaj9tI9glcOE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZUfJRg18JUtdhTwJdqWkX1WmgsRwwCgHR3lQFKyt5II/T9h92ZNF4dorTjT85adRW dpH+XjF77F1tuDHjjukTbCbhqJyUTB8UZwgD9gKpy8sGklkFfZn5BrgACrGAdJjNjr QUE5XLgIAe1lH+PiUacKYMgTvDrZMKeQkGpkfrbw= From: "dumoulin.thibaut at gmail dot com" 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 07:00:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.9.3 X-Bugzilla-Keywords: patch X-Bugzilla-Severity: enhancement X-Bugzilla-Who: dumoulin.thibaut at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68606 Thibaut M. changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dumoulin.thibaut at gmail = dot com --- Comment #10 from Thibaut M. --- I understand the patch https://gcc.gnu.org/legacy-ml/gcc-patches/2016-12/msg01158.html has not been applied. The dynamic constructor of global variable `pool emergency_pool;` in `libstdc++-v3/libsupc++/eh_alloc.cc` remains and is still allocating unconditionally at least 2.5ko on the heap. > see the "performance of exception handling" / "size of exception handling" > thread in this month's archive of the gcc mailing list I was not able to find the thread about "exception handling" of 2020-05, co= uld you point it out or detail the conclusion please? 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 po= ol not needed.=