public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87489] [8/9/10/11 Regression] Spurious -Wnonnull warning
Date: Thu, 18 Feb 2021 16:20:47 +0000	[thread overview]
Message-ID: <bug-87489-4-vT4F07gHvS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87489-4@http.gcc.gnu.org/bugzilla/>

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

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|msebor at gcc dot gnu.org          |law at gcc dot gnu.org
   Target Milestone|11.0                        |12.0

--- Comment #15 from Jeffrey A. Law <law at redhat dot com> ---
I'm explicitly pushing this out of gcc-11.  As I've mentioned in the thread for
Martin's patch, reordering passes is generally not the right approach to
solving most issues.

I've got a proof-of-concept improvement to the jump threader that nearly
catches this case that I'm attaching to this case so it doesn't get lost.  The
most important missing bit in that patch is when we have two statements in a
block that must be considered, it gives up.  While that was a reasonable
limitation in the past, it's one we need to fix anyway and this BZ is a good
motivator.

While I'm confident that could be fixed and that we'd handle this issue, I'm
not comfortable dropping in improvements like this into gcc-11 at this stage. 
Hence the explicit deferment to gcc-12.

  parent reply	other threads:[~2021-02-18 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-87489-4@http.gcc.gnu.org/bugzilla/>
2021-02-01  0:01 ` msebor at gcc dot gnu.org
2021-02-01  0:24 ` msebor at gcc dot gnu.org
2021-02-01  0:35 ` msebor at gcc dot gnu.org
2021-02-18 16:20 ` law at redhat dot com [this message]
2021-02-19 23:38 ` msebor at gcc dot gnu.org
2022-05-06  8:30 ` [Bug middle-end/87489] [9/10/11/12/13 " jakub at gcc dot gnu.org
2022-12-05 15:27 ` [Bug middle-end/87489] [10/11/12/13 " rguenth at gcc dot gnu.org
2023-05-08 12:21 ` [Bug middle-end/87489] [10/11/12/13/14 " 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-87489-4-vT4F07gHvS@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).