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/106626] Improvements to wording of -Wanalyzer-out-of-bounds Date: Mon, 15 Aug 2022 18:48:57 +0000 [thread overview] Message-ID: <bug-106626-4-6Xf1T3dbAs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106626-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626 --- Comment #1 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:23e8c0b0d99f585499baddda70af6a8b26f49bea commit r13-2054-g23e8c0b0d99f585499baddda70af6a8b26f49bea Author: David Malcolm <dmalcolm@redhat.com> Date: Mon Aug 15 14:47:03 2022 -0400 analyzer: fix direction of -Wanalyzer-out-of-bounds note [PR106626] Fix a read/write typo. Also, add more test coverage of -Wanalyzer-out-of-bounds to help establish a baseline for experiments on tweaking the wording of the warning (PR analyzer/106626). gcc/analyzer/ChangeLog: PR analyzer/106626 * region-model.cc (buffer_overread::emit): Fix copy&paste error in direction of the access in the note. gcc/testsuite/ChangeLog: PR analyzer/106626 * gcc.dg/analyzer/out-of-bounds-read-char-arr.c: New test. * gcc.dg/analyzer/out-of-bounds-read-int-arr.c: New test. * gcc.dg/analyzer/out-of-bounds-write-char-arr.c: New test. * gcc.dg/analyzer/out-of-bounds-write-int-arr.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-08-15 18:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-15 13:08 [Bug analyzer/106626] New: " dmalcolm at gcc dot gnu.org 2022-08-15 18:48 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-01 2:31 ` [Bug analyzer/106626] " cvs-commit at gcc dot gnu.org 2022-12-01 2:31 ` cvs-commit at gcc dot gnu.org 2022-12-01 2:31 ` cvs-commit at gcc dot gnu.org 2022-12-01 2:31 ` cvs-commit at gcc dot gnu.org 2022-12-01 2:31 ` cvs-commit at gcc dot gnu.org 2023-04-07 12:36 ` dmalcolm at gcc dot gnu.org 2023-06-22 2:06 ` cvs-commit 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-106626-4-6Xf1T3dbAs@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).