From: Sergei Trofimovich <slyfox@gentoo.org>
To: gcc-patches@gcc.gnu.org
Cc: Richard Biener <rguenther@suse.de>, Jan Hubicka <jh@suse.cz>,
Sergei Trofimovich <siarheit@google.com>
Subject: [PATCH] ipa-modref: avoid linebreak split in debug print
Date: Thu, 7 Jan 2021 23:07:58 +0000 [thread overview]
Message-ID: <20210107230758.3110298-1-slyfox@gentoo.org> (raw)
From: Sergei Trofimovich <siarheit@google.com>
* ipa-modref.c (merge_call_side_effects): Fix
linebreak split by reordering two print calls.
---
gcc/ipa-modref.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/ipa-modref.c b/gcc/ipa-modref.c
index fcc676d25e4..04613201f1f 100644
--- a/gcc/ipa-modref.c
+++ b/gcc/ipa-modref.c
@@ -835,10 +835,6 @@ merge_call_side_effects (modref_summary *cur_summary,
auto_vec <modref_parm_map, 32> parm_map;
bool changed = false;
- if (dump_file)
- fprintf (dump_file, " - Merging side effects of %s with parm map:",
- callee_node->dump_name ());
-
/* We can not safely optimize based on summary of callee if it does
not always bind to current def: it is possible that memory load
was optimized out earlier which may not happen in the interposed
@@ -850,6 +846,10 @@ merge_call_side_effects (modref_summary *cur_summary,
cur_summary->loads->collapse ();
}
+ if (dump_file)
+ fprintf (dump_file, " - Merging side effects of %s with parm map:",
+ callee_node->dump_name ());
+
parm_map.safe_grow_cleared (gimple_call_num_args (stmt), true);
for (unsigned i = 0; i < gimple_call_num_args (stmt); i++)
{
--
2.30.0
next reply other threads:[~2021-01-07 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 23:07 Sergei Trofimovich [this message]
2021-01-08 8:46 ` Richard Biener
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=20210107230758.3110298-1-slyfox@gentoo.org \
--to=slyfox@gentoo.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=rguenther@suse.de \
--cc=siarheit@google.com \
/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).