From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B033B385783F; Tue, 16 May 2023 02:44:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B033B385783F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684205053; bh=aGoR4hpKbn0KT9qZr/Je6124NsHgo70AgOCd0AGkKss=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XGa3tg/N51N3L6g/G3G32MhozZ0fdQ/8HhkD716Z36jtjz1138YeuIO72s7hNzMaF VpyS7tzFmjK6bXoXIJpFS4O6GShC83g2g9IOZvNS451Pnnzwd0gIwA6O3QpBmgAAEZ NNH9oY/0n5/6UmL+3d0wYxU+h0xdR8wpI6nLOcvk= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109863] RFE: more consistent flex array initialization: lift static storage requirement in gnu2x Date: Tue, 16 May 2023 02:44:13 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org 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: 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=3D109863 --- Comment #2 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #1) > Note that the entire "initializing a flexible array member" thing is a GNU > extension and not supported by the standard. So GCC is free to support t= he > constexpr case but reject other non-static cases. Or, "it's an extension after all, so it's not related to if the standard say constexpr implies static or not".=