public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4407] Improve uninit diagnostic dumps
Date: Wed, 30 Nov 2022 11:53:28 +0000 (GMT)	[thread overview]
Message-ID: <20221130115329.02B80385781F@sourceware.org> (raw)

https://gcc.gnu.org/g:2792cb50f55529e1737461e032ed13e7f04f73d2

commit r13-4407-g2792cb50f55529e1737461e032ed13e7f04f73d2
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Nov 30 12:03:56 2022 +0100

    Improve uninit diagnostic dumps
    
    The following dumps the edge a use is uninitialized in a PHI.
    
            * tree-ssa-uninit.cc (find_uninit_use): Dump the edge for a
            PHI node.

Diff:
---
 gcc/tree-ssa-uninit.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/tree-ssa-uninit.cc b/gcc/tree-ssa-uninit.cc
index bf2e50511af..7fbc384f2d4 100644
--- a/gcc/tree-ssa-uninit.cc
+++ b/gcc/tree-ssa-uninit.cc
@@ -1249,8 +1249,8 @@ find_uninit_use (gphi *phi, unsigned uninit_opnds, int *bb_to_rpo)
 
 	  if (dump_file && (dump_flags & TDF_DETAILS))
 	    {
-	      fprintf (dump_file, "Found unguarded use in bb %u: ",
-		       use_bb->index);
+	      fprintf (dump_file, "Found unguarded use on edge %u -> %u: ",
+		       e->src->index, e->dest->index);
 	      print_gimple_stmt (dump_file, use_stmt, 0);
 	    }
 	  /* Found a phi use that is not guarded, mark the phi_result as

                 reply	other threads:[~2022-11-30 11:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221130115329.02B80385781F@sourceware.org \
    --to=rguenth@gcc.gnu.org \
    --cc=gcc-cvs@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).