public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steveire at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108499] New: False positive -Warray-bounds
Date: Mon, 23 Jan 2023 15:28:22 +0000	[thread overview]
Message-ID: <bug-108499-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108499
           Summary: False positive -Warray-bounds
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: steveire at gmail dot com
  Target Milestone: ---

```

#include <vector>

class MyStruct
{
public:
    std::vector<double> const& refAccessor();
    std::size_t getSize();
};

void emitsWarning()
{
    MyStruct params;

    auto unusedThing = params.refAccessor();
    (void)unusedThing;
    auto const theSize = params.getSize();

    std::vector<double> initialVelocities(theSize, 0.0);
    initialVelocities.back() = 6;
    std::vector<double> initialJoints(theSize, 0.0);
    initialJoints.back() = 5;
}

```

-Werror=array-bounds  -O2

```
<source>: In function 'void emitsWarning()':
<source>:20:27: error: array subscript -1 is outside array bounds of 'double
[1152921504606846975]' [-Werror=array-bounds]
   20 |     initialVelocities.back() = 6;
      |     ~~~~~~~~~~~~~~~~~~~~~~^~
cc1plus: some warnings being treated as errors
Compiler returned: 1
```

https://gcc.godbolt.org/z/sYrK6o54a

             reply	other threads:[~2023-01-23 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 15:28 steveire at gmail dot com [this message]
2023-01-23 16:03 ` [Bug tree-optimization/108499] " pinskia at gcc dot gnu.org
2023-01-24 11:01 ` steveire at gmail dot com
2023-01-24 11:02 ` steveire at gmail dot com

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-108499-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).