This is the mail archive of the
mailing list for the GCC project.
Re: [gofrontend-dev] GO tools for gccgo cross
- From: "Lynn A. Boger" <laboger at linux dot vnet dot ibm dot com>
- To: Ian Lance Taylor <iant at golang dot org>
- Cc: "gofrontend-dev at googlegroups dot com" <gofrontend-dev at googlegroups dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 14 Apr 2015 08:14:14 -0500
- Subject: Re: [gofrontend-dev] GO tools for gccgo cross
- Authentication-results: sourceware.org; auth=none
- References: <54D1270A dot 9050607 at linux dot vnet dot ibm dot com> <CAOyqgcWQwrM5Z2w9KZSFc7ASdp=YFHZzXL01ovRwuG2PSAvaqw at mail dot gmail dot com> <ec194a29-a888-44df-b466-46c7ea06c7f2 at googlegroups dot com> <CAOyqgcWm1t+8VF4Ae9_fhaVPXciriftux1e6MjVvjJ8wJeYHLA at mail dot gmail dot com>
I got sidetracked with some bug fixes and decided the change for this
was not real small.
Should this be submitted to gofrontend, or to the golang master source?
On 03/17/2015 01:27 PM, Ian Lance Taylor wrote:
On Tue, Mar 17, 2015 at 7:36 AM, <firstname.lastname@example.org> wrote:
I have a patch to get gccgo to work on cross.
Is it too late to try and get this into gcc 5.0?
I think it's still possible. Depends on how small and safe it is.
On Tuesday, February 3, 2015 at 2:18:39 PM UTC-6, Ian Lance Taylor wrote:
On Tue, Feb 3, 2015 at 11:52 AM, Lynn A. Boger
I've been experimenting with the go tools and how to make them work for
cross gccgo builds.
In golang I think there is just one 'go' tool and the cross build
are specified by the setting of GOARCH and GOOS. So why couldn't the
be done with gccgo?
That means, on any given system, I think we just need to build the
gccgo and the go tools that are built with it. No need to build
go tools for each cross target. If a cross build is needed, then set
GOARCH and GOOS values appropriately and invoke the native go (for
tool. Source changes are needed for the go tool source to determine the
correct cross compiler name based on the GOARCH and GOOS settings, and
use that cross compiler where needed for building or linking instead of
always using "gccgo". I was able to make these changes and get this to
-- I built gccgo programs targeted for ppc64le on an x86_64.
I agree that setting GOARCH and GOOS should change the default name of
the gccgo compiler that the go tool uses.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an
email to email@example.com.
For more options, visit https://groups.google.com/d/optout.