Hey, Peter, thanks for keeping me in the loop on your presentation. One
comment: if gcc-go has problems or
is generating faulty binaries, you should create a defect in the gcc-go
community. My colleague
Bill and others are willing and eager to work these.
-Jeff
Jeffrey J. Scheel
From: Peter Lemenkov <lemenkov(a)gmail.com>
To: Vincent Batts <vbatts(a)redhat.com>,
Cc: golang(a)lists.fedoraproject.org, erlang(a)lists.fedoraproject.org,
Jeffrey Scheel/Rochester/IBM@IBMUS
Date: 11/09/2013 02:19 AM
Subject: Re: Slides from my future talk at Moscow Golang User Group
meetup
2013/11/8 Vincent Batts <vbatts(a)redhat.com>:
On 08/11/13 12:01 +0100, Dan Hor?k wrote:
> Is there a strict dependency on golang or just on go? Because
"GCC
> 4.8.2 provides a complete implementation of the Go 1.1.2 release."
> citing from gcc 4.8.2 release notes and we build gccgo on all our
> secondary arches.
gccgo will compile on any arch it is available, while the golang
compiler has a more limited scope. So far the golang libraries that are
packaged are source only, so anyone wanting to build with gccgo, need
only set up their compile flags to -I the directories of the libraries
needed.
As I said there is an problem - gcc-go does compile just fine, but the
resulting binary will refuse to run due to (maybe artificial)
limitations in the golang source code. (Un)fortunately gcc-go shares a
lot of code with golang itself so it doesn't add much to the hardware
support.
--
With best regards, Peter Lemenkov.