public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8736] AArch64: Fix bootstrap failure due to dump_printf_loc format attribute uses [PR106782]
Date: Fri,  2 Sep 2022 08:23:35 +0000 (GMT)	[thread overview]
Message-ID: <20220902082335.6420D3858C54@sourceware.org> (raw)

https://gcc.gnu.org/g:e69134e12551a4289292e3955525f84d99773d31

commit r12-8736-ge69134e12551a4289292e3955525f84d99773d31
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Thu Sep 1 22:04:57 2022 +0100

    AArch64: Fix bootstrap failure due to dump_printf_loc format attribute uses [PR106782]
    
    This fixes the bootstrap failure on AArch64 following -Werror=format by
    correcting the print format modifiers in the backend.
    
    gcc/ChangeLog:
    
            PR other/106782
            * config/aarch64/aarch64.cc
            (aarch64_vector_costs::prefer_unrolled_loop): Replace %u with
            HOST_WIDE_INT_PRINT_UNSIGNED.
    
    (cherry picked from commit b98c5262d02c13cdbbf3b985859b436adec94d90)

Diff:
---
 gcc/config/aarch64/aarch64.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 5c9e7791a12..ac1153e31af 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -16677,7 +16677,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-02  8:23 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=20220902082335.6420D3858C54@sourceware.org \
    --to=tnfchris@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).