public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jun at junz dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110204] New: Suspicous warning when compiling ranges-v3 using GCC trunk (iteration 9223372036854775807 invokes undefined behavior)
Date: Sat, 10 Jun 2023 14:41:03 +0000	[thread overview]
Message-ID: <bug-110204-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110204
           Summary: Suspicous warning when compiling ranges-v3 using GCC
                    trunk (iteration 9223372036854775807 invokes undefined
                    behavior)
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jun at junz dot org
  Target Milestone: ---

Given code:

#include <vector>
#include <map>
#include <range/v3/all.hpp>

std::map<int, int> m;

std::vector<int> foo() {
  return ranges::to<std::vector>(m | ranges::views::keys);
}

GCC trunk reports:

/opt/compiler-explorer/gcc-trunk-20230610/include/c++/14.0.0/bits/stl_iterator_base_funcs.h:175:9:
warning: iteration 9223372036854775807 invokes undefined behavior
[-Waggressive-loop-optimizations]
  175 |         while (__n--)
      |         ^~~~~
/opt/compiler-explorer/gcc-trunk-20230610/include/c++/14.0.0/bits/stl_iterator_base_funcs.h:175:9:
note: within this loop

while Clang and GCC 13 both say OK. I think this is a regression.
goldbolt link: https://godbolt.org/z/W33aMqr5c

             reply	other threads:[~2023-06-10 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 14:41 jun at junz dot org [this message]
2023-06-10 15:54 ` [Bug tree-optimization/110204] " pinskia at gcc dot gnu.org
2023-06-10 15:54 ` [Bug tree-optimization/110204] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-15  3:34 ` pinskia at gcc dot gnu.org
2023-07-15  3:48 ` pinskia at gcc dot gnu.org
2023-07-15  3:56 ` pinskia at gcc dot gnu.org
2023-07-17  9:55 ` rguenth at gcc dot gnu.org
2023-07-19 13:12 ` rguenth at gcc dot gnu.org
2023-07-20 12:46 ` cvs-commit at gcc dot gnu.org
2023-07-20 12:55 ` 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-110204-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).