public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adam.f.badura at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111087] New: -Wnonnull issued for std::array of zero size when under C++20
Date: Mon, 21 Aug 2023 06:29:17 +0000	[thread overview]
Message-ID: <bug-111087-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111087
           Summary: -Wnonnull issued for std::array of zero size when
                    under C++20
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: adam.f.badura at gmail dot com
  Target Milestone: ---

At least for GCC 10.2 and 12.2, when using -std=c++20 I'm getting unexpected
-Wnonnull in the following (simplified) case:

  #include <algorithm>
  #include <array>
  #include <string_view>

  const std::array<std::string_view, 0> tags{};

  bool hasTag(const char* const tag)
  {
    const auto result = std::lower_bound(tags.begin(), tags. End(), tag);
    return result != tags.end() && result->compare(tag) == 0;
  }

See it on Compiler Explorer: https://godbolt.org/z/rGenGef7n.

It seems to be associated with the 0 size of the array since as soon as I
change it to 1 (or more) the warning goes away. Same if I drop the -std=c++20
(for 12.2 - with 10.2 it will not work due to <string_view>).

             reply	other threads:[~2023-08-21  6:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  6:29 adam.f.badura at gmail dot com [this message]
2023-08-21  6:33 ` [Bug c++/111087] " pinskia at gcc dot gnu.org
2023-08-21  6:53 ` adam.f.badura at gmail dot com
2023-08-21  7:26 ` pinskia at gcc dot gnu.org
2023-08-21  7:27 ` pinskia at gcc dot gnu.org
2023-08-21  7:31 ` adam.f.badura at gmail dot com
2023-08-21  7:39 ` pinskia at gcc dot gnu.org
2023-08-21  7:47 ` adam.f.badura at gmail dot com
2023-08-21  7:54 ` pinskia at gcc dot gnu.org
2023-08-21  8:03 ` adam.f.badura at gmail dot com
2023-08-21 10:31 ` redi at gcc dot gnu.org
2023-08-21 10:36 ` redi 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-111087-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).