From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 481473858C1F; Fri, 2 Dec 2022 16:36:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 481473858C1F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669999011; bh=mDGh8Svj8bfDKaReoJZvh1Lzzb2/THCNb5Grh5MaEVM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j0UM+t+5kK4g7XNM4kiUi0NtOUTcFsOByPFdcxLZ/YtAi9WCon5fIKDF70Hup5Rx1 kiUnAdF5H6BY31AA0RTWMujdxAm5BXNsMCnFP6eMsrTwK8w/ReZup79D5BXQrihiTz UrGPpSIfE8pQpALI/UtCrfJ/XEteSMKaQ4CTrkwg= From: "siddhesh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107951] Invalid flexible array use not detected in nested structs by the C frontend Date: Fri, 02 Dec 2022 16:36:51 +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.0 X-Bugzilla-Keywords: accepts-invalid X-Bugzilla-Severity: normal X-Bugzilla-Who: siddhesh at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: bug_status resolution 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=3D107951 Siddhesh Poyarekar changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Siddhesh Poyarekar --- (In reply to Andrew Pinski from comment #3) > r0-44662-g2984fe64968ad7 added that documentation. > PR 15749 shows that at one point there was code floating around (glibc?) > that uses the extension (_G_iconv_t). Yeah but it doesn't address bug 77650, which I agree that this is a duplica= te of. Thanks for pointing out! *** This bug has been marked as a duplicate of bug 77650 ***=