On Tue, Apr 14, 2015 at 6:14 AM, Lynn A. Boger <labo...@linux.vnet.ibm.com> wrote: > 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?
Let's try it in the master repo. Thanks. Ian > On 03/17/2015 01:27 PM, Ian Lance Taylor wrote: >> >> On Tue, Mar 17, 2015 at 7:36 AM, <labo...@linux.vnet.ibm.com> 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. >> >> Ian >> >> >>> 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 >>>> <lab...@linux.vnet.ibm.com> wrote: >>>>> >>>>> 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 >>>>> targets >>>>> are specified by the setting of GOARCH and GOOS. So why couldn't the >>>>> same >>>>> be done with gccgo? >>>>> >>>>> That means, on any given system, I think we just need to build the >>>>> native >>>>> gccgo and the go tools that are built with it. No need to build >>>>> different >>>>> go tools for each cross target. If a cross build is needed, then set >>>>> the >>>>> GOARCH and GOOS values appropriately and invoke the native go (for >>>>> gccgo) >>>>> 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 >>>>> then >>>>> 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 >>>>> work >>>>> -- 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. >>>> >>>> Ian >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "gofrontend-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to gofrontend-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >
