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 F18D03858D39; Mon,  8 Apr 2024 13:07:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F18D03858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712581624;
	bh=sYQHIMkOUNsksmvCs8Ixv29l5XQn57kLzn0jX6ymMuA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XG4mZZWcVBOgP3P3oPUo++2uLSYKEGoJ8i1q0xnPn370Cey4F4Ytu4zz1zOjDt21e
	 V9Zs+mTynQBrSy1XjDqeiOR2vKyapFv8TJUUvWqmdMAUN+giCfwmPyUnX1t2viBxb1
	 ciYHSm7D7QzV8e7aYnIY10qYxOGwLZdHFn6D/li8=
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 13:07:03 +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-u7C9tUnl5I@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 #26 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 #25 from Douglas Boffey <douglas.boffey at gmail dot com> ---
> (In reply to rguenther@suse.de from comment #24)
> > dumpbin /headers executable.exe
>=20
> ...
>           C00000 size of stack reserve

OK, so that's the expected 12MB we adjust the stack reserve to.  It's
odd that you run into stack exhaustion (or maybe you don't and instead
run out of other memory).

I've now tried GCC 11.4 as you reportedly used on x86_64-linux and
can compile the testcase successfully with that using 2GB memory
and 75s compile-time.  Stack usage itself isn't measured but 8MB
were enough.

GCC 13 runs out of (8MB) stack for me.=