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/99474] New: missing warning on an out of bounds VLA access by a pointer
Date: Mon, 08 Mar 2021 21:36:29 +0000	[thread overview]
Message-ID: <bug-99474-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99474
           Summary: missing warning on an out of bounds VLA access by a
                    pointer
           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 out of bounds access in both functions below should be diagnosed by
-Warray-bounds but only the first one is.

$ cat v.c && gcc -O2 -S -Wall v.c
void f (void*);

void g (void)
{
  int a[5];
  int *p = &a[0];
  p[5] = 0;        // -Warray-bounds (good)
  f (a);
}

void h (int n)
{
  if (n > 5)
    n = 5;
  int a[n];
  int *p = &a[0];
  p[5] = 0;        // missing warning
  f (a);
}

v.c: In function ‘g’:
v.c:7:4: warning: array subscript 5 is outside array bounds of ‘int[5]’
[-Warray-bounds]
    7 |   p[5] = 0;        // -Warray-bounds (good)
      |   ~^~~
v.c:5:7: note: while referencing ‘a’
    5 |   int a[5];
      |       ^

             reply	other threads:[~2021-03-08 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 21:36 msebor at gcc dot gnu.org [this message]
2021-04-02 17:30 ` [Bug tree-optimization/99474] " 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-99474-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).