From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: jakub@redhat.com
Subject: [pushed] vect: Fix stray argument in call to dump_printf_loc
Date: Wed, 31 Aug 2022 09:20:04 +0100 [thread overview]
Message-ID: <mpt1qswesej.fsf@arm.com> (raw)
One call to dump_printf_loc had a stray left-over argument
from an earlier version of the patch. This went unnoticed
on aarch64-linux-gnu and x86_64-linux-gnu since the parameters
that actually mattered were passed in FPRs rather than GPRs,
but I assume this is the reason for the i686-linux-gnu failures
that Jakub hit.
Tested on x86_64-linux-gnu & pushed as obvious. Sorry for the breakage.
Richard
gcc/
* tree-vect-slp.cc (vect_optimize_slp_pass::dump): Remove bogus
argument.
---
gcc/tree-vect-slp.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/tree-vect-slp.cc b/gcc/tree-vect-slp.cc
index ab4c6fa6776..226550635cc 100644
--- a/gcc/tree-vect-slp.cc
+++ b/gcc/tree-vect-slp.cc
@@ -5461,7 +5461,7 @@ vect_optimize_slp_pass::dump ()
combined_cost.add_serial_cost (layout_costs.out_cost);
#define TEMPLATE "{depth: %f, total: %f}"
dump_printf_loc (MSG_NOTE, vect_location,
- " " TEMPLATE "\n", layout_i,
+ " " TEMPLATE "\n",
layout_costs.in_cost.depth.to_double (),
layout_costs.in_cost.total.to_double ());
dump_printf_loc (MSG_NOTE, vect_location,
--
2.25.1
reply other threads:[~2022-08-31 8:20 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=mpt1qswesej.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).