public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108517] [11/12/13 Regression] std::sort of empty range yield "warning: 'this' pointer is null"
Date: Tue, 24 Jan 2023 13:01:43 +0000	[thread overview]
Message-ID: <bug-108517-4-9rYFFz0AvZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108517-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org
            Summary|std::sort of empty range    |[11/12/13 Regression]
                   |yield "warning: 'this'      |std::sort of empty range
                   |pointer is null"            |yield "warning: 'this'
                   |                            |pointer is null"
      Known to fail|                            |11.1.0
      Known to work|                            |10.4.0

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The warning started with r11-1697:

  Underline argument in -Wnonnull and in C++ extend warning to the this pointer
[PR c++/86568].

  Resolves:
  PR c++/86568 - -Wnonnull warnings should highlight the relevant argument not
the closing parenthesis

  parent reply	other threads:[~2023-01-24 13:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 12:01 [Bug libstdc++/108517] New: " hanicka at hanicka dot net
2023-01-24 12:33 ` [Bug libstdc++/108517] " redi at gcc dot gnu.org
2023-01-24 12:35 ` redi at gcc dot gnu.org
2023-01-24 12:37 ` [Bug c++/108517] " redi at gcc dot gnu.org
2023-01-24 12:41 ` redi at gcc dot gnu.org
2023-01-24 13:01 ` redi at gcc dot gnu.org [this message]
2023-01-24 13:07 ` [Bug c++/108517] [11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-02-01 12:32 ` jakub at gcc dot gnu.org
2023-02-01 12:40 ` jakub at gcc dot gnu.org
2023-02-15 15:28 ` jamborm at gcc dot gnu.org
2023-02-21 12:59 ` rguenth at gcc dot gnu.org
2023-05-29 10:07 ` [Bug c++/108517] [11/12/13/14 " jakub 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-108517-4-9rYFFz0AvZ@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).