From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C12B43858D20; Mon,  8 Apr 2024 09:54:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C12B43858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712570042;
	bh=ch3Ew3wWDhaIKqWpXh83fOBpc0MILlKIv278exX4Sjk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tJxIZkwE302X+tbDkhVZpGCywcHomTNzQUFQieVPAVBK2BTX0418q7npRvHBWY/vT
	 /mYja9Byb2L/TZSOcdLM5w539eHvg4toNaJdhP6FMyYZ0JIQNTCJq0kGtDbgXi2IU8
	 w2YlEzA3rKsNMPejw8UrTFy/8ARohYtrgrbzo/zs=
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114480] g++: internal compiler error: Segmentation fault
 signal terminated program cc1plus
Date: Mon, 08 Apr 2024 09:54:00 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 11.4.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114480-4-GNEpHYl1ap@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114480-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114480-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #24 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 8 Apr 2024, douglas.boffey at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114480
>=20
> --- Comment #23 from Douglas Boffey <douglas.boffey at gmail dot com> ---
> (In reply to Richard Biener from comment #22)
> > Note we're using -Wl,--stack,12582912 when linking the GCC executables,=
 I
> > wonder
> > if the reporter can verify the segfaulting executables have the correct=
 stack
> > size set?
>=20
> How do I find that out?

googling tells me

dumpbin /headers executable.exe

which should show a "size of stack reserve".  Alternatively if you
have objdump from binutils that might also show this info.  Basically
it's encoded in the binary (you want to check cc1plus.exe here).

There's also

editbin /stack:N executable.exe

where you can alter the stack reserve of the binary to N=