public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andre Simoes Dias Vieira <avieira@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-4684] tree-cfg: Add count information when creating new bb in move_sese_region_to_fn
Date: Tue, 17 Oct 2023 14:22:49 +0000 (GMT)	[thread overview]
Message-ID: <20231017142249.12C773858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:305034e3ae9499264c539ec14529e849eef7d725

commit r14-4684-g305034e3ae9499264c539ec14529e849eef7d725
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date:   Tue Oct 17 15:02:29 2023 +0100

    tree-cfg: Add count information when creating new bb in move_sese_region_to_fn
    
    This patch makes sure the profile_count information is initialized for the new
    bb created in move_sese_region_to_fn.
    
    gcc/ChangeLog:
    
            * tree-cfg.cc (move_sese_region_to_fn): Initialize profile_count for
            new basic block.

Diff:
---
 gcc/tree-cfg.cc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/tree-cfg.cc b/gcc/tree-cfg.cc
index ffab7518b156..ffeb20b717ae 100644
--- a/gcc/tree-cfg.cc
+++ b/gcc/tree-cfg.cc
@@ -8160,11 +8160,14 @@ move_sese_region_to_fn (struct function *dest_cfun, basic_block entry_bb,
   bb = create_empty_bb (entry_pred[0]);
   if (current_loops)
     add_bb_to_loop (bb, loop);
+  profile_count count = profile_count::zero ();
   for (i = 0; i < num_entry_edges; i++)
     {
       e = make_edge (entry_pred[i], bb, entry_flag[i]);
       e->probability = entry_prob[i];
+      count += e->count ();
     }
+  bb->count = count;
 
   for (i = 0; i < num_exit_edges; i++)
     {

                 reply	other threads:[~2023-10-17 14:22 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=20231017142249.12C773858D33@sourceware.org \
    --to=avieira@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).