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 r12-1446] Assert we have irreducible regions marked in the threader
Date: Tue, 15 Jun 2021 08:29:47 +0000 (GMT)	[thread overview]
Message-ID: <20210615082947.D22ED3989004@sourceware.org> (raw)

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

commit r12-1446-gb10f895f41dbe98f2a7d448b91d083a68792a6a0
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 15 10:27:47 2021 +0200

    Assert we have irreducible regions marked in the threader
    
    This adds an assert that would fire if any thread path registry
    user runs into the check that relies on such regions marked.
    
    2021-06-15  Richard Biener  <rguenther@suse.de>
    
            * tree-ssa-threadupdate.c
            (jump_thread_path_registry::mark_threaded_blocks): Assert we
            have marked irreducible regions.

Diff:
---
 gcc/tree-ssa-threadupdate.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c
index a86302be18e..f496dd3eb8c 100644
--- a/gcc/tree-ssa-threadupdate.c
+++ b/gcc/tree-ssa-threadupdate.c
@@ -2122,6 +2122,8 @@ jump_thread_path_registry::mark_threaded_blocks (bitmap threaded_blocks)
 	{
 	  if (e->aux)
 	    {
+	      gcc_assert (loops_state_satisfies_p
+			    (LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS));
 	      vec<jump_thread_edge *> *path = THREAD_PATH (e);
 
 	      for (unsigned int i = 0, crossed_headers = 0;


                 reply	other threads:[~2021-06-15  8:29 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=20210615082947.D22ED3989004@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).