From: Jim Wilson <jimw@sifive.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Ian Lance Taylor <iant@golang.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
gofrontend-dev <gofrontend-dev@googlegroups.com>
Subject: Re: Go patch committed: Intrinsify runtime/internal/atomic functions
Date: Thu, 30 May 2019 20:56:00 -0000 [thread overview]
Message-ID: <CAFyWVabFqHd7L85Pku-v+DS6WqzHLNcAD_BGqLHWwBCRVw05Cw@mail.gmail.com> (raw)
In-Reply-To: <87zhn395ix.fsf@igel.home>
On Thu, May 30, 2019 at 11:11 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
> Here are the test results:
> http://gcc.gnu.org/ml/gcc-testresults/2019-05/msg02903.html
I tried running RISC-V go checks on my system. I see 7 unexpected
failures for gcc check-go, 6 unexpected failures for check-gotools,
and 1 unexpected failure for check-target-libgo. I haven't tried
building and testing the go support before so I don't have any old
results to compare against. It seems reasonable for a first attempt
though.
Jim
next prev parent reply other threads:[~2019-05-30 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 0:21 Ian Lance Taylor
2019-05-19 12:22 ` Andreas Schwab
2019-05-22 1:17 ` Jim Wilson
2019-05-23 1:37 ` [gofrontend-dev] " Cherry Zhang via gcc-patches
2019-05-23 1:41 ` Ian Lance Taylor
2019-05-30 20:50 ` Jim Wilson
2019-05-30 20:51 ` Jim Wilson
2019-05-30 18:37 ` Andreas Schwab
2019-05-30 20:56 ` Jim Wilson [this message]
2019-06-03 14:12 ` Maciej Rozycki
2019-06-03 17:03 ` Ian Lance Taylor
2019-06-03 20:11 ` Maciej Rozycki
2019-06-03 17:21 ` Andreas Schwab
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=CAFyWVabFqHd7L85Pku-v+DS6WqzHLNcAD_BGqLHWwBCRVw05Cw@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.org \
--cc=schwab@linux-m68k.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).