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-2639] tree-optimization/106913 - ICE with -da and -Wuninitialized
Date: Tue, 13 Sep 2022 08:52:36 +0000 (GMT)	[thread overview]
Message-ID: <20220913085236.E3D463850866@sourceware.org> (raw)

https://gcc.gnu.org/g:ad08894ea02b6308c4ed4e8cd8e6a564c2f581e8

commit r13-2639-gad08894ea02b6308c4ed4e8cd8e6a564c2f581e8
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Sep 13 08:46:51 2022 +0200

    tree-optimization/106913 - ICE with -da and -Wuninitialized
    
    The following avoids setting and not clearing an auto_bb_flag
    on EXIT_BLOCK which we don't verify for such stale flags but
    dump_bb_info still asserts on them.
    
            PR tree-optimization/106913
            * tree-ssa-uninit.cc (warn_uninitialized_vars): Do not set
            ft_reachable on EXIT_BLOCK.

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

diff --git a/gcc/tree-ssa-uninit.cc b/gcc/tree-ssa-uninit.cc
index 4a1c333d9cb..eae29f88f9d 100644
--- a/gcc/tree-ssa-uninit.cc
+++ b/gcc/tree-ssa-uninit.cc
@@ -1013,11 +1013,9 @@ warn_uninitialized_vars (bool wmaybe_uninit)
       if (ee)
 	bb = ee->dest;
       else
-	{
-	  bb = get_immediate_dominator (CDI_POST_DOMINATORS, bb);
-	  if (!bb || bb->index == EXIT_BLOCK)
-	    break;
-	}
+	bb = get_immediate_dominator (CDI_POST_DOMINATORS, bb);
+      if (!bb || bb->index == EXIT_BLOCK)
+	break;
     }
 
   FOR_EACH_BB_FN (bb, cfun)

                 reply	other threads:[~2022-09-13  8:52 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=20220913085236.E3D463850866@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).