From: "Marc Poulhiès" <dkm+gcc@kataplop.net>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: Philip Herron <philip.herron@embecosm.com>, gcc@gcc.gnu.org
Subject: Re: GCC Rust git branch
Date: Fri, 28 May 2021 13:48:59 +0200 [thread overview]
Message-ID: <87tumnnkno.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <0f00f1f4-aadd-20ac-f140-8cba7ed73a25@embecosm.com> (Philip Herron's message of "Fri, 28 May 2021 11:18:20 +0100")
Philip Herron <philip.herron@embecosm.com> writes:
> On 28/05/2021 04:05, Thomas Fitzsimmons wrote:
>> Hi Philip,
>>
>> Philip Herron <philip.herron@embecosm.com> writes:
>>
>>> As some of you might know, I have been working on GCC Rust over on
>>> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
>>> forward and enforcing GCC copyright assignments for contributors, I
>>> would like to create a branch on the GCC git repo to show the intention
>>> to be upstream with GCC someday.
>> I tried building GCC Rust on ppc64le. With the attached patches,
>> "make check-rust" succeeds with:
>>
>> === rust Summary ===
>>
>> # of expected passes 2368
>> # of expected failures 26
>>
>> Thomas
>>
> Hi Thomas,
>
> Thank you so much for doing this, we will merge these later today. The
> results look the same as the numbers were getting on x86 too.
Hello,
FYI, your changes are being merged : https://github.com/Rust-GCC/gccrs/pull/454
Thanks!
Marc
next prev parent reply other threads:[~2021-05-28 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:24 Philip Herron
2021-05-24 16:24 ` Joseph Myers
2022-06-08 12:36 ` Thomas Schwinge
2021-05-24 18:29 ` Mark Wielaard
2021-05-28 10:31 ` Philip Herron
2021-05-30 22:33 ` Mark Wielaard
2021-05-28 3:05 ` Thomas Fitzsimmons
2021-05-28 10:18 ` Philip Herron
2021-05-28 11:48 ` Marc Poulhiès [this message]
2021-05-30 22:49 ` Mark Wielaard
2021-05-28 3:22 ` Jason Merrill
2021-05-28 10:19 ` Philip Herron
2022-06-08 10:58 ` Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch) Thomas Schwinge
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=87tumnnkno.fsf@arrakis.kataplop.net \
--to=dkm+gcc@kataplop.net \
--cc=fitzsim@fitzsim.org \
--cc=gcc@gcc.gnu.org \
--cc=philip.herron@embecosm.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).