public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106868] [12/13 Regression] Bogus -Wdangling-pointer warning with -O1
Date: Mon, 12 Sep 2022 17:04:24 +0000	[thread overview]
Message-ID: <bug-106868-4-TmHGGqCIrA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106868-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #2)
...
Actually, scratch that, sorry.  Richard is right that the false positive is due
to a bug in the warning code.  The following patch resolves it:

diff --git a/gcc/gimple-ssa-warn-access.cc b/gcc/gimple-ssa-warn-access.cc
index 04aa849a4b1..79093b46906 100644
--- a/gcc/gimple-ssa-warn-access.cc
+++ b/gcc/gimple-ssa-warn-access.cc
@@ -4467,6 +4467,7 @@ pass_waccess::gimple_call_return_arg_ref (gcall *call)
     {
       access_ref aref;
       if (m_ptr_qry.get_ref (arg, call, &aref, 0)
+         && aref.deref < 0
          && DECL_P (aref.ref))
        return aref.ref;
     }

  parent reply	other threads:[~2022-09-12 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  8:47 [Bug c/106868] New: " medhefgo at web dot de
2022-09-07  9:05 ` [Bug tree-optimization/106868] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-09-12 16:18 ` msebor at gcc dot gnu.org
2022-09-12 17:04 ` msebor at gcc dot gnu.org [this message]
2022-12-05  9:41 ` rguenth at gcc dot gnu.org
2022-12-05 13:56 ` cvs-commit at gcc dot gnu.org
2022-12-05 14:06 ` rguenth at gcc dot gnu.org
2022-12-12 11:20 ` [Bug tree-optimization/106868] [12 " cvs-commit at gcc dot gnu.org
2022-12-12 11:20 ` 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-106868-4-TmHGGqCIrA@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).