From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B436A3858C2F; Thu, 29 Sep 2022 07:02:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B436A3858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664434946; bh=ZjMisECQwiuQl8udLzbRPxplRTmg37GuPs0cdhvbD4c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Et/R7vTNCMpejR6pdO2zX9MCGr8Ryzy0Mj0js7iJGaY7+2l6FS3Ps6A1RdrbTSF/N 1HRcSbiJgVpMPjCCSBe4oUpn8aqSFLXvmws4FpvPGb+RihNH+u7M+tJUgAGY23HstX 5QJHM9gSI1Ovvxqvu8ORy/RIxe2E2Ugpuq5xLb2M= From: "rguenth at gcc dot 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 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: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 --- Comment #16 from Richard Biener --- (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): T= here > > 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. >=20 > 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. >=20 > Let's try to do that for GCC 13. Any such solution would also be OK to backport I think.=