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 43AAB385840F; Mon,  8 Apr 2024 09:46:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 43AAB385840F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712569591;
	bh=qE+KjlaqNKQHsLMtqyJMdNflXj/fzvLgSLa0PZV+pcg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=oV9vFoJqg0Sjp8jaNTCu3glDZfIYcZFoj5nD4unLnhddUgwPP/12xeB++6dJr8NGp
	 p6GQIHYeZcOFAOlrxkkq1HiDraqJ4DaJvXSysMGj8JiO0RC+FaEnIyMMFMQTIZ4si0
	 /rfnAq7vgwUhBGgYAmlZrdopBlZFwxMIS4UrxP50=
From: "rguenth at gcc dot gnu.org" <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:46:25 +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: rguenth at gcc dot gnu.org
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-9BB7JcsjC7@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 #22 from Richard Biener <rguenth at gcc dot gnu.org> ---
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 sta=
ck
size set?=