From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2778F3857BB2; Mon, 15 May 2023 16:30:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2778F3857BB2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684168236; bh=H9uFxCHz6HBlm1zZzSBLdLXQGQWvAo8GLlzVr+SGIVQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TuqlmQZxLBHlujSQSBZhudKGTzRt8ZDozZ9s4o4a6h03jXUYbDh3ybKLqMtjXqCtE +yrUnriMqMCNSkju7CfcesqRBvhprtE+qousB8Xs4RK4rw/EA4w+LvlPxsOlKt1jYz eHykBPQs4U3Z68eCnVm1bklykCzKQR04CzfAdDEE= From: "yann at droneaud dot fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109828] [13/14 Regression] static compound literal with flexible array in initializer leads to invalid size and ICE Date: Mon, 15 May 2023 16:30:36 +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: 13.1.0 X-Bugzilla-Keywords: accepts-invalid, assemble-failure, ice-checking, ice-on-invalid-code, needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: yann at droneaud dot fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109828 --- Comment #8 from Yann Droneaud --- (In reply to Yann Droneaud from comment #7) > I've also experimented compound literal initialization at block level > instead of file level. Except in case it's not supported, it shows the sa= me > issue at block level as file level. >=20 > https://godbolt.org/z/vn5Pn7hTx >=20 > Unrelated, I've noted it's not possible to initialize the flexible array = if > the initializer is not having a static storage. I would have expected this > restriction to be lifted by now. I've opened bug #109863=