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 tree-optimization/99502] missing -Warray-bounds on partial out of bounds access in C++
Date: Thu, 18 Mar 2021 19:38:32 +0000	[thread overview]
Message-ID: <bug-99502-4-R5e8FgtpfH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99502-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99502

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:30b10dacd0a8c926c22eab7d4aeb52ff86534acf

commit r11-7724-g30b10dacd0a8c926c22eab7d4aeb52ff86534acf
Author: Martin Sebor <msebor@redhat.com>
Date:   Thu Mar 18 13:36:09 2021 -0600

    PR middle-end/99502 - missing -Warray-bounds on partial out of bounds

    gcc/ChangeLog:

            PR middle-end/99502
            * gimple-array-bounds.cc (inbounds_vbase_memaccess_p): Rename...
            (inbounds_memaccess_p): ...to this.  Check the ending offset of
            the accessed member.

    gcc/testsuite/ChangeLog:

            PR middle-end/99502
            * g++.dg/warn/Warray-bounds-22.C: New test.
            * g++.dg/warn/Warray-bounds-23.C: New test.
            * g++.dg/warn/Warray-bounds-24.C: New test.

  parent reply	other threads:[~2021-03-18 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  0:58 [Bug tree-optimization/99502] New: " msebor at gcc dot gnu.org
2021-03-10  0:58 ` [Bug tree-optimization/99502] " msebor at gcc dot gnu.org
2021-03-18 19:38 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-18 19:39 ` msebor 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-99502-4-R5e8FgtpfH@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: link
Be 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).