From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: Jan Hubicka <hubicka@ucw.cz>
Subject: [PATCH] Fix print_loop_info ICE
Date: Mon, 14 Aug 2023 08:35:49 +0000 (UTC) [thread overview]
Message-ID: <20230814083549.42w8P474soysGxt83-oEWJDnqmMcltVt0EXQjqG1M_0@z> (raw)
It ICEs when invoked via debug_loops and dump_file clear.
Pushed as obvious.
* tree-cfg.cc (print_loop_info): Dump to 'file', not 'dump_file'.
---
gcc/tree-cfg.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/tree-cfg.cc b/gcc/tree-cfg.cc
index ab1f8067c54..fae80bb5b91 100644
--- a/gcc/tree-cfg.cc
+++ b/gcc/tree-cfg.cc
@@ -8565,7 +8565,7 @@ print_loop_info (FILE *file, const class loop *loop, const char *prefix)
fprintf (file, "\n%siterations by profile: %f (%s%s) entry count:", prefix,
iterations.to_double (), reliable ? "reliable" : "unreliable",
maybe_flat_loop_profile (loop) ? ", maybe flat" : "");
- loop_count_in (loop).dump (dump_file, cfun);
+ loop_count_in (loop).dump (file, cfun);
}
}
--
2.35.3
reply other threads:[~2023-08-14 8:35 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=20230814083549.42w8P474soysGxt83-oEWJDnqmMcltVt0EXQjqG1M_0@z \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).