public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1308
Date: Tue, 21 Jun 2022 10:33:19 +0000 (GMT)	[thread overview]
Message-ID: <20220621103319.7EF91383F952@sourceware.org> (raw)

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

commit d4a0780073bfaf96d72427d5138b74ef257ed625
Merge: 08e407e977e 29f57496698
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Jun 17 06:39:03 2022 +0000

    Merge #1308
    
    1308: Fix formatting error on 32-bits targets r=CohenArthur a=dkm
    
    Printing size_t as [unsigned] long (%ld or %lu) raises warnings on 32-bits
    targets. As the GCC pretty printer doesn't have the equivalent of libc's %z/%zu,
    fix all formats to use unsigned long and cast values.
    
    refs #1229
    
    Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
    Co-authored-by: Rainer Orth <ro@gcc.gnu.org>
    
    Co-authored-by: Marc Poulhiès <dkm@kataplop.net>

Diff:

 gcc/rust/expand/rust-macro-expand.cc              |  6 ++--
 gcc/rust/expand/rust-macro-substitute-ctx.cc      |  7 +++--
 gcc/rust/lex/rust-lex.cc                          |  2 +-
 gcc/rust/lint/rust-lint-marklive.cc               |  4 +--
 gcc/rust/rust-session-manager.cc                  |  4 +--
 gcc/rust/typecheck/rust-hir-type-check-pattern.cc | 11 ++++---
 gcc/rust/typecheck/rust-tyty.cc                   | 37 ++++++++++++++---------
 7 files changed, 41 insertions(+), 30 deletions(-)


                 reply	other threads:[~2022-06-21 10:33 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=20220621103319.7EF91383F952@sourceware.org \
    --to=tschwinge@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).