This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot
- From: "Maciej W. Rozycki" <macro at wdc dot com>
- To: Ulderico Cirello <uldericofilho at gmail dot com>
- Cc: gcc-patches at gcc dot gnu dot org, libffi-discuss at sourceware dot org, golang-dev <golang-dev at googlegroups dot com>
- Date: Mon, 11 Nov 2019 18:42:27 +0000 (GMT)
- Subject: Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot
- Ironport-sdr: urB5x5EPOBjPB2Ri99mDdOH0nYWq1m4AdywomZ/PwhlxGYdhmLyfS/BDi21amsqvWZ5FCouO5o kdAbioANkU5gE6LfVPebm/WZ5DsImjsBdtYpeftnw2n/G/4zA0tpA8ayN1jc8C+ZZES1G9SEyM LsGVSef/HFmesphBFuxSgvi+qz16v0CEkNOnz4FIsPBa+yKa0bMMf3CSBNwCA0dpGjvN/y4dyR My1/SLoesgGR8xkTB3iJzHnEkVp1Gr/9sGuNvjyim8/QvvRgZ6v8VySSkUlJnOP1S+2VMYSKvW hfA=
- Ironport-sdr: kL0cdFvpTrPPeu5Ozrc0zu6eJ4TQzC3OA9kWWun7FqxrjzYDCGmlwwCBA3bOCgOf8HGCrE8fBX XaoLZFVpsUNK1xbWhu2Wr10ZDkQKgwZXjh2DaITA1Z0DkvgyaOnOa66f1eEeW4eULAIyrFItYc wwdCyybhilK6esqAqDxgSm889SDXAl9UFFZd/dtQFOt2n4NizlL//rIzSMz3NZZpYRxPoi3Mbu Xq08gJVrhgplwn8/grSK00Xp2Y3no9auL5BT9O4iYdUywevJ+h/yCPgvYjgtCe5UHxyVWN64Wv l3xDCBL7VX4YvgIQ7N0rr/Xu
- Ironport-sdr: i312i22CCTzHPg0JZerG/Lw8lDp0krv4emaSvJ2AEVTm/wTD3SDmImX2fasclZ4ZAy/Lfw+ywM 0MjjOBQcI+zx4AgfKOtublxNwpYzVGBxQJJPMeCv94JiUopxnlS9ErdqbAT8noOKV9TgTrAGOG grHF/goIA4q9wRjpEhErwrjaw+PP2QKaUHS801pJYJQ1lQGyfrVJklNIZ6Q99mIiSeAWksdtJm ZuzLWWFhDhkS+qGZNUb6vNf5gDdQelrBETUdMeKqASj6vH2HeZXMHhjpe77F3Sdf2Ziq6AfcFv hhM=
- References: <alpine.LFD.2.21.1911081714120.13542@redsun52.ssa.fujisawa.hgst.com> <CALe9M7m6YhdNqm+wZY9qKbFHQ-o=ePYn9hnC+Lf-+4ZjVWdOTQ@mail.gmail.com>
- Wdcironportexception: Internal
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