public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102196] -Wmaybe-uninitialized: Maybe generate helpful hints?
Date: Fri, 03 Sep 2021 19:59:46 +0000	[thread overview]
Message-ID: <bug-102196-4-rpz08aCdUm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102196-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
          Component|middle-end                  |tree-optimization
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2021-09-03
           Keywords|                            |diagnostic

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
They should show the usage of the variable and where the declaration of the
variable is.
Can you show what output you get from compiling binutils?
Maybe even attach the preprocessed source.

  reply	other threads:[~2021-09-03 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 19:35 [Bug middle-end/102196] New: " jbglaw@lug-owl.de
2021-09-03 19:59 ` pinskia at gcc dot gnu.org [this message]
2021-09-03 20:20 ` [Bug tree-optimization/102196] " jbglaw@lug-owl.de
2021-09-03 20:34 ` pinskia at gcc dot gnu.org
2021-09-03 21:16 ` egallager at gcc dot gnu.org
2021-09-03 22:14 ` msebor at gcc dot gnu.org
2021-09-04 14:44 ` jbglaw@lug-owl.de

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-102196-4-rpz08aCdUm@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).