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 d/96989] SSA_NAMEs in Wuninitialized warning messages after r11-959
Date: Wed, 09 Sep 2020 17:11:05 +0000	[thread overview]
Message-ID: <bug-96989-4-0e4rkG3HAx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96989-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The MEM_REF formatting done by the C and C++ pretty-printers is very basic and
doesn't always result in useful output (usually in the most interesting cases).

I posted a patch some time ago to improve it for C++ (as part of fix for an ICE
reported in pr95768):
https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548698.html

Richi had some concerns with it but I think it's a significant improvement
despite them.  I plan to extend the C++-only patch to C and post it again at
some point when I'm done with stage 1 work.  If it's approved it should be
straightforward to use the same approach in the D front end (in fact, all front
ends should share the same code for this).

  parent reply	other threads:[~2020-09-09 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 22:06 [Bug d/96989] New: " ibuclaw at gdcproject dot org
2020-09-09  6:47 ` [Bug d/96989] " rguenth at gcc dot gnu.org
2020-09-09  9:11 ` ibuclaw at gdcproject dot org
2020-09-09 17:11 ` msebor at gcc dot gnu.org [this message]
2020-09-17 10:23 ` ibuclaw at gdcproject dot org
2021-08-06 22:22 ` [Bug middle-end/96989] " msebor at gcc dot gnu.org
2021-08-06 22:24 ` msebor 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-96989-4-0e4rkG3HAx@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).