This is the mail archive of the
mailing list for the GCC project.
Re: Go in gcc 4.7
Richard Guenther <firstname.lastname@example.org> writes:
> On Wed, Jan 11, 2012 at 5:43 AM, Ian Lance Taylor <email@example.com> wrote:
>> The Go language is closing in what we are calling Go version 1. ÂThis
>> will be a long-term stable release of Go, with no language or library
>> API changes. ÂGo 1 is described here:
> There is still no official ABI, right? So no chance of different Go
> to interoperate? Are the ABIs that the different implementations use documented
It doesn't make too much sense to speak of an official ABI for Go in
general. gccgo uses the usual C ABI on any given system. The way that
gccgo represents Go types in C terms is documented at:
http://golang.org/doc/gccgo_install.html#C_Interoperability . Though,
as noted, some of the implementations are still subject to change, so in
that sense there is no final ABI.
The 6g and gccgo compilers are never going to interoperate. 6g uses a
different approach to compilation, a different object file format, a
different calling convention, etc., all in the name of fast compilation
rather than fast execution.
> Definitely though this is worth mentioning in gcc-4.7/changes.html.
Yes, will do.