public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104060] [11/12 Regression] -Wmaybe-uninitialized false alarm on address of local array
Date: Mon, 17 Jan 2022 08:45:02 +0000	[thread overview]
Message-ID: <bug-104060-4-ODHAiX3Hx9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104060-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
                 CC|                            |hubicka at gcc dot gnu.org,
                   |                            |msebor at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note we can eventually use modref info in the "wrong way" to query whether the
argument is dereferenced.  Note it can only alswer the question whether it
may be dereferenced or whether it kills (via stores) a specific range based on
it, both are not an exact match here since modref will conservatively say
the argument is dereferenced.

But I agree with Andrew - with the above we could make the warning only trigger
for local functions GCC saw the body for (or with LTO bodies analyzed during
IPA but now in another LTRANS unit).  That should eventually reduce the number
of false positives.

  parent reply	other threads:[~2022-01-17  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17  3:41 [Bug tree-optimization/104060] New: " eggert at cs dot ucla.edu
2022-01-17  3:49 ` [Bug tree-optimization/104060] [11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-17  8:45 ` rguenth at gcc dot gnu.org [this message]
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug tree-optimization/104060] [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-104060-4-ODHAiX3Hx9@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).