public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99502] New: missing -Warray-bounds on partial out of bounds access in C++
Date: Wed, 10 Mar 2021 00:58:37 +0000	[thread overview]
Message-ID: <bug-99502-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99502
           Summary: missing -Warray-bounds on partial out of bounds access
                    in C++
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

The program below triggers two instances of -Warray-bounds when compiled as C
code but only one when compiled as C++.  This is a regression introduced in 
r11-7563.

$ cat u.C && gcc -O2 -S -Wall u.C
typedef struct A { int i; } A;

char a[sizeof (A) - 1];

void f (A x)
{
  A *p = (A*)a;
  *p = x;          // -Warray-bounds (good)
}

void g (void)
{
  A *p = (A*)a;
  p->i = 0;        // missing warning in C++
}

u.C: In function ‘void f(A)’:
u.C:8:6: warning: array subscript ‘A[0]’ is partly outside array bounds of
‘char [3]’ [-Warray-bounds]
    8 |   *p = x;          // -Warray-bounds (good)
      |   ~~~^~~
u.C:3:6: note: while referencing ‘a’
    3 | char a[sizeof (A) - 1];
      |      ^

             reply	other threads:[~2021-03-10  0:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  0:58 msebor at gcc dot gnu.org [this message]
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
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@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).