public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/loop-unswitch-improvement-v7)] Do not use auto_vec when passing..
Date: Wed,  8 Dec 2021 18:25:57 +0000 (GMT)	[thread overview]
Message-ID: <20211208182557.38ABA3858003@sourceware.org> (raw)

https://gcc.gnu.org/g:0d2e9f0d9def25c5e4b38e74570b6b4a9dc06159

commit 0d2e9f0d9def25c5e4b38e74570b6b4a9dc06159
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Dec 1 15:13:31 2021 +0100

    Do not use auto_vec when passing..

Diff:
---
 gcc/tree-ssa-loop-unswitch.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gcc/tree-ssa-loop-unswitch.c b/gcc/tree-ssa-loop-unswitch.c
index 9a0ecb6f999..4eb5e442da4 100644
--- a/gcc/tree-ssa-loop-unswitch.c
+++ b/gcc/tree-ssa-loop-unswitch.c
@@ -101,7 +101,8 @@ static vec<vec<unswitch_predicate *>> *bb_predicates = NULL;
 static gimple_ranger *ranger = NULL;
 
 /* The type represents a predicate path leading to a basic block.  */
-typedef auto_vec<std::pair<unswitch_predicate *, bool>> predicate_vector;
+typedef vec<std::pair<unswitch_predicate *, bool>> auto_predicate_vector;
+typedef vec<std::pair<unswitch_predicate *, bool>> predicate_vector;
 
 static class loop *tree_unswitch_loop (class loop *, basic_block, tree);
 static bool tree_unswitch_single_loop (class loop *, int,
@@ -200,7 +201,7 @@ tree_ssa_unswitch_loops (void)
 	  unsigned int budget
 	    = init_loop_unswitch_info (loop) + param_max_unswitch_insns;
 
-	  predicate_vector predicate_path;
+	  auto_predicate_vector predicate_path;
 	  changed |= tree_unswitch_single_loop (loop, 0, predicate_path,
 						budget);


             reply	other threads:[~2021-12-08 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 18:25 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-09 12:48 Martin Liska
2021-12-08 10:17 Martin Liska
2021-12-07 16:49 Martin Liska

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=20211208182557.38ABA3858003@sourceware.org \
    --to=marxin@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).