public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alex Coplan <acoplan@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-1503] btf: Fix -Wformat errors
Date: Fri,  2 Jun 2023 16:03:21 +0000 (GMT)	[thread overview]
Message-ID: <20230602160321.757CE3858D32@sourceware.org> (raw)

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

commit r14-1503-gf2e60a00c7c017bd87ba9afb189cbb77d8c92925
Author: Alex Coplan <alex.coplan@arm.com>
Date:   Fri Jun 2 16:58:19 2023 +0100

    btf: Fix -Wformat errors
    
    g:7aae58b04b92303ccda3ead600be98f0d4b7f462 introduced -Wformat errors
    breaking bootstrap on some targets. This patch fixes that.
    
    Committed as obvious.
    
    gcc/ChangeLog:
    
            * btfout.cc (btf_asm_type): Use PRIu64 instead of %lu for uint64_t.
            (btf_asm_datasec_type): Likewise.

Diff:
---
 gcc/btfout.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/btfout.cc b/gcc/btfout.cc
index f51ccf73242..1ea68b9e8ba 100644
--- a/gcc/btfout.cc
+++ b/gcc/btfout.cc
@@ -799,7 +799,7 @@ btf_asm_type (ctf_container_ref ctfc, ctf_dtdef_ref dtd)
    }
 
   dw2_asm_output_data (4, dtd->dtd_data.ctti_name,
-		       "TYPE %lu BTF_KIND_%s '%s'",
+		       "TYPE %" PRIu64 " BTF_KIND_%s '%s'",
 		       get_btf_id (dtd->dtd_type), btf_kind_name (btf_kind),
 		       dtd->dtd_name);
   dw2_asm_output_data (4, BTF_TYPE_INFO (btf_kind, btf_kflag, btf_vlen),
@@ -967,7 +967,7 @@ btf_asm_datasec_type (ctf_container_ref ctfc, btf_datasec_t ds, ctf_id_t id,
 		      size_t stroffset)
 {
   dw2_asm_output_data (4, ds.name_offset + stroffset,
-		       "TYPE %lu BTF_KIND_DATASEC '%s'",
+		       "TYPE %" PRIu64 " BTF_KIND_DATASEC '%s'",
 		       btf_absolute_datasec_id (id), ds.name);
   dw2_asm_output_data (4, BTF_TYPE_INFO (BTF_KIND_DATASEC, 0,
 					 ds.entries.length ()),

                 reply	other threads:[~2023-06-02 16: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=20230602160321.757CE3858D32@sourceware.org \
    --to=acoplan@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).