public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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 15:47:43 +0000 [thread overview] Message-ID: <bug-107951-4-Mvi8dPpaaP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107951-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107951 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- 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).
next prev parent reply other threads:[~2022-12-02 15:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-02 13:28 [Bug c/107951] New: " siddhesh at gcc dot gnu.org 2022-12-02 14:44 ` [Bug c/107951] " rguenth at gcc dot gnu.org 2022-12-02 15:38 ` qinzhao at gcc dot gnu.org 2022-12-02 15:47 ` pinskia at gcc dot gnu.org [this message] 2022-12-02 15:50 ` pinskia at gcc dot gnu.org 2022-12-02 16:36 ` siddhesh at gcc dot gnu.org 2022-12-02 16:51 ` qinzhao at gcc dot gnu.org 2022-12-02 16:55 ` jakub at gcc dot gnu.org 2022-12-02 17:01 ` qinzhao at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107951-4-Mvi8dPpaaP@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).