public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/98247] RFE: detect Flexible Array Member misuse in analyzer Date: Fri, 09 Sep 2022 21:11:03 +0000 [thread overview] Message-ID: <bug-98247-4-LYubdhLTRM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98247-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98247 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:084dc9a0c6cec14596093ad077fc3e25c6b99bc3 commit r13-2571-g084dc9a0c6cec14596093ad077fc3e25c6b99bc3 Author: David Malcolm <dmalcolm@redhat.com> Date: Fri Sep 9 17:10:08 2022 -0400 analyzer: add test coverage for flexible array members [PR98247] gcc/testsuite/ChangeLog: PR analyzer/98247 * gcc.dg/analyzer/flexible-array-member-1.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-09-09 21:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-11 16:32 [Bug c/98247] New: gcc analyzer does not detect Flexible Array Member misuse vince.a.bridgers at gmail dot com 2021-03-19 14:08 ` [Bug analyzer/98247] RFE: detect Flexible Array Member misuse in analyzer dmalcolm at gcc dot gnu.org 2022-08-26 18:00 ` dmalcolm at gcc dot gnu.org 2022-08-26 18:04 ` dmalcolm at gcc dot gnu.org 2022-09-09 21:11 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-09 21:44 ` [Bug analyzer/98247] Analyzer fails to detect certain out-of-bounds uses of flexible array members dmalcolm 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-98247-4-LYubdhLTRM@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).