From: "Maciej W. Rozycki" <macro@wdc.com>
To: Ulderico Cirello <uldericofilho@gmail.com>
Cc: gcc-patches@gcc.gnu.org, libffi-discuss@sourceware.org,
golang-dev <golang-dev@googlegroups.com>
Subject: Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot
Date: Mon, 11 Nov 2019 18:42:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1911111824140.13542@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <CALe9M7m6YhdNqm+wZY9qKbFHQ-o=ePYn9hnC+Lf-+4ZjVWdOTQ@mail.gmail.com>
On Mon, 11 Nov 2019, Ulderico Cirello wrote:
> Go's project doesn't take mail patches for changes. Please use gerrit (
> https://go-review.googlesource.com/ ).
Thanks for your reply; this is however too much effort for my limited
resources and a one-off change.
The reason is I'm not actively working on Go and I have only enabled Go
frontend compilation/verification for my RISC-V effort in case there is a
regression caused by a machine backend change that happens to only trigger
for the Go frontend so that it does not go unnoticed.
I have provided this change in a hope it is useful to the community and
in these circumstances hopefully someone actually interested in Go will
pick up and merge this change; otherwise I will drop my local change and
consequently Go verification once GCC 10 has been released.
Thank you for your understanding.
Maciej
prev parent reply other threads:[~2019-11-11 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:12 Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 1/4] libatomic/test: Fix " Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 2/4] libffi/test: " Maciej W. Rozycki
2019-11-11 18:15 ` [golang-dev] [PATCH 0/4] Fix library testsuite " Ulderico Cirello
2019-11-11 18:23 ` Kaz Kylheku (libffi)
2019-11-11 18:35 ` Ian Lance Taylor
2019-11-11 18:50 ` Kaz Kylheku (libffi)
2019-11-11 18:33 ` Ian Lance Taylor
2019-11-11 18:44 ` Maciej W. Rozycki
2019-11-11 23:16 ` Ian Lance Taylor
2019-11-11 18:42 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.1911111824140.13542@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=golang-dev@googlegroups.com \
--cc=libffi-discuss@sourceware.org \
--cc=uldericofilho@gmail.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).