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 92B433858D32; Mon, 12 Jun 2023 18:11:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 92B433858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1686593501;
	bh=tln64F1Vt1ey0NzBaPRPd5Tfz/ntaOkrEsxJdyni4r0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=eQRJ7GIncSsI2jqUQfF/Zx8AFRXrma3LfMmBp4uDQe9dI1/j+o0T+ysjLlr59MGcu
	 TZ1fGst3QK8tMRUE3q7s3k+78+Ar3CvCLU4q3HC3EdDwrM/M/xb7x49clakNjW4nVu
	 6u9ig8cg7PNwCQRRtXJY8Z9yQ2RlwO09WKkBRV+c=
From: "larry9 at ffdlr dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110229] Segment fault with initializer an array
 (unrolled) in a function
Date: Mon, 12 Jun 2023 18:11:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: GC, ice-on-valid-code, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: larry9 at ffdlr dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110229-4-wkFrV3lK9G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110229-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=3D110229

--- Comment #4 from Larry Fiedler <larry9 at ffdlr dot com> ---
Yes, I should have experimented with changing the stack size.
The structure is now done as an initializer list of an array with no proble=
ms.=