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 #1228
Date: Wed,  8 Jun 2022 12:45:24 +0000 (GMT)	[thread overview]
Message-ID: <20220608124524.F320D3895FD9@sourceware.org> (raw)

https://gcc.gnu.org/g:8d828e4b301a52e43246176848ae8869dd26255c

commit 8d828e4b301a52e43246176848ae8869dd26255c
Merge: 140f6a698b4 dd213da6a3b
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon May 9 14:32:00 2022 +0000

    Merge #1228
    
    1228: Fix match tests on 32bit systems r=philberty a=philberty
    
    Printing i64's on 32bit systems requires the proper format specifier
    this amends these test cases to 32bit integers so %i works as expected.
    I was able to use gdb to verify that these values are computed properly
    from the structure on 32 bit systems.
    
    Keeping the structures as i32 we can ignore platform-specific format
    specifiers.
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/testsuite/rust/execute/torture/match1.rs | 2 +-
 gcc/testsuite/rust/execute/torture/match3.rs | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


                 reply	other threads:[~2022-06-08 12:45 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=20220608124524.F320D3895FD9@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).