public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "byteslice at airmail dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105420] New: Bogus -Warray-bounds with non-compile time-constant variable
Date: Thu, 28 Apr 2022 13:21:43 +0000	[thread overview]
Message-ID: <bug-105420-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105420
           Summary: Bogus -Warray-bounds with non-compile time-constant
                    variable
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: byteslice at airmail dot cc
  Target Milestone: ---

Created attachment 52894
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52894&action=edit
Reduced example

On gcc 12.0.1 20220413 (Fedora 36 Beta), with c++ -O1 -fexpensive-optimizations
-ftree-vrp -Werror=array-bounds, the attachment fails to compile, with the
following message:

<source>: In function 'void Initialize(int)':
<source>:9:53: error: array subscript -1 is below array bounds of 'int [8]'
[-Werror=array-bounds]
    9 |   int phys_core = VirtualToPhysicalCoreMap[virt_core];
      |                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
<source>:2:5: note: while referencing 'VirtualToPhysicalCoreMap'
    2 | int VirtualToPhysicalCoreMap[8];
      |     ^~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: some warnings being treated as errors
Compiler returned: 1

virt_core does not have a compile time-constant evaluation, so this warning is
bogus. The bogus warning does not appear in older versions of GCC.

Removing either -fexpensive-optimizations or -ftree-vrp allows compilation to
succeed.

             reply	other threads:[~2022-04-28 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 13:21 byteslice at airmail dot cc [this message]
2022-04-29  6:26 ` [Bug tree-optimization/105420] " rguenth at gcc dot gnu.org
2022-04-29 11:42 ` byteslice at airmail dot cc

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