From: Tamar Christina <tamar.christina@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: nd@arm.com, Richard.Earnshaw@arm.com, Marcus.Shawcroft@arm.com,
Kyrylo.Tkachov@arm.com, richard.sandiford@arm.com
Subject: [PATCH][committed]AArch64 Fix bootstrap failure due to dump_printf_loc format attribute uses [PR106782]
Date: Thu, 1 Sep 2022 22:03:12 +0100 [thread overview]
Message-ID: <patch-16190-tamar@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hi All,
This fixes the bootstrap failure on AArch64 following -Werror=format by
correcting the print format modifiers in the backend.
Bootstrapped on aarch64-none-linux-gnu and no issues.
Committed as obvious.
Thanks,
Tamar
gcc/ChangeLog:
PR other/106782
* config/aarch64/aarch64.cc
(aarch64_vector_costs::prefer_unrolled_loop): Replace %u with
HOST_WIDE_INT_PRINT_UNSIGNED.
--- inline copy of patch --
diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 4b486aeea90ea2afb9cdd96a4dbe15c5bb2abd7a..f199e77cd4296cd3556641051072dabc9f5e51fa 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -16671,7 +16671,8 @@ aarch64_vector_costs::prefer_unrolled_loop () const
if (dump_enabled_p ())
dump_printf_loc (MSG_NOTE, vect_location, "Number of insns in"
- " unrolled Advanced SIMD loop = %d\n",
+ " unrolled Advanced SIMD loop = "
+ HOST_WIDE_INT_PRINT_UNSIGNED "\n",
m_unrolled_advsimd_stmts);
/* The balance here is tricky. On the one hand, we can't be sure whether
--
[-- Attachment #2: rb16190.patch --]
[-- Type: text/plain, Size: 664 bytes --]
diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 4b486aeea90ea2afb9cdd96a4dbe15c5bb2abd7a..f199e77cd4296cd3556641051072dabc9f5e51fa 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -16671,7 +16671,8 @@ aarch64_vector_costs::prefer_unrolled_loop () const
if (dump_enabled_p ())
dump_printf_loc (MSG_NOTE, vect_location, "Number of insns in"
- " unrolled Advanced SIMD loop = %d\n",
+ " unrolled Advanced SIMD loop = "
+ HOST_WIDE_INT_PRINT_UNSIGNED "\n",
m_unrolled_advsimd_stmts);
/* The balance here is tricky. On the one hand, we can't be sure whether
reply other threads:[~2022-09-01 21:03 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=patch-16190-tamar@arm.com \
--to=tamar.christina@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=richard.sandiford@arm.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).