public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sss@li-snyder.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112767] New: [14 regression] spurious -Waggressive-loop-optimizations
Date: Wed, 29 Nov 2023 18:24:49 +0000	[thread overview]
Message-ID: <bug-112767-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112767
           Summary: [14 regression] spurious
                    -Waggressive-loop-optimizations
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sss@li-snyder.org
  Target Milestone: ---

With a recent checkout of gcc14 (20231129), on a x86_64-pc-linux-gnu host,
the following source gives a seemingly bogus -Waggressive-loop-optimizations
warning with -O3:

--------------------------------------------------------------
double reg_dict[32];

void foo(int);

void initialize()
{
  int i=8;
  for (int phi=0; phi<8; ++phi) {
    reg_dict[i]=0;
    int sn = 0;
    if (i < 16) sn = 20;
    foo(sn);
    ++i;
  }
}
--------------------------------------------------------------

$ g++ -c -O3 x.cc
x.cc: In function ‘void initialize()’:
x.cc:9:16: warning: iteration 16 invokes undefined behavior
[-Waggressive-loop-optimizations]
    9 |     reg_dict[i]=0;
      |     ~~~~~~~~~~~^~
x.cc:8:22: note: within this loop
    8 |   for (int phi=0; phi<8; ++phi) {
      |                   ~~~^~


This is a confusing warning, as the containing loop is executed only 8 times.
Exactly which undefined behavior is meant is also not spelled out.
From the context, i'd guess it to be an out-of-bounds array write,
but that's a false positive.

The warning happens with -O3 but not with lower optimization levels.
It also does not occur with gcc 13.2.1 20230728.

             reply	other threads:[~2023-11-29 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 18:24 sss@li-snyder.org [this message]
2023-11-29 18:34 ` [Bug tree-optimization/112767] " pinskia at gcc dot gnu.org
2023-11-29 22:08 ` ppalka at gcc dot gnu.org
2023-11-30 11:42 ` [Bug tree-optimization/112767] [14 regression] spurious -Waggressive-loop-optimizations since r14-2944-g3d48c11ad082de rguenth at gcc dot gnu.org
2023-11-30 12:35 ` cvs-commit at gcc dot gnu.org
2023-11-30 12:36 ` rguenth 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-112767-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).