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 407493858C33; Wed, 19 Jul 2023 14:06:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 407493858C33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689775587;
	bh=EyvaBL21vaKJJ0iNOSUa+RYqlh0WCBCCnxQTqReuUu8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=suacxO+SvVMkozZTYwAIkXmmDZalyZnIOuJR3fo0f3AX9mOjys5loDDEvwHtk8Qbk
	 TzJfJgAdk1HZABT+yhWvojZQBZzcgAf/Vl/8j3awetTtK9oHs5VIHRb7aWJwKOpaPE
	 /2HGSh7PRWq9Kw1+x+A81fAT+p7WiBEsQdqHUAOk=
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110315] [13 Regression] g++ crashes with a
 segmentation fault while compiling a large const std::vector of std::string
 since r13-6566-ge0324e2629e25a90
Date: Wed, 19 Jul 2023 14:06:26 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.1.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amacleod at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110315-4-NdmNxDYCIc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110315-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110315-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=3D110315

--- Comment #3 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Richard Biener from comment #2)
> Confirmed.  Not sure whether it's possible to backport any of the stack
> usage reduction in ranger from trunk or whether it's other recursion
> limiting that
> avoids this there (besides different IL from the frontend ...).
>=20
> Andrew/Aldy?  The call chain is 20000 frames deep when it faults on me
> (with a -O0 built cc1plus running in gdb).

I'll have a look=