public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: jlec@gentoo.org
Subject: Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform
Date: Wed, 4 Nov 2015 17:46:29 -0600	[thread overview]
Message-ID: <20151104234629.GA21846@whubbs1.ad.gaikai.biz> (raw)
In-Reply-To: <20151103150952.61db1304@red.yakaraplc.local>

[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]

On Tue, Nov 03, 2015 at 03:09:52PM +0000, James Le Cuirot wrote:
> On Tue, 3 Nov 2015 08:56:29 -0600
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > As has been pointed out in the thread so far, gcc-5 only supports
> > go-1.4. dev-lang/go is at 1.5, so really the only thing that should be
> > built with gccgo is dev-lang/go. Also, the golang eclasses are
> > designed to work with dev-lang/go, so they do not need a dependency
> > on gccgo.
> > 
> > I see gcc-5[go] as a separate Go compiler, but it will always be
> > behind dev-lang/go, so you will have things that build with
> > dev-lang/go but not gccgo. Also, the commands to do the builds are
> > completely different depending on which one you are using.
> 
> This is a lot like the situation with gcc's gcj and the icedtea Java
> JDK. The arguments are quite different so we have a wrapper script
> packaged as gcj-jdk. gcj only supports Java 6(ish?) and there are
> other compatibility issues though so we no longer support it as a
> general purpose JDK. Its only use is for bootstrapping icedtea. Now
> that Java has been open sourced and gcj has fallen so far behind, gcc
> are planning to scrap it so icedtea will need to find another way to
> bootstrap (probably JamVM) if it isn't to rely on prebuilt versions of
> itself.

I am definitely not against the patch to enable gccgo on all platforms.
This actually may make it possible for us to bootstrap dev-lang/go on
all of the platforms gccgo can be built on.

However, the situation with gcj sounds very similar to what is happening
with Go, and I want to take the same approach.

I do not recommend using gccgo as a general-purpose Go compiler. I may
be able to use it to bootstrap the general purpose compiler, which is
dev-lang/go, but That will probably be about it since it will always
be behind.

I am against virtual/go. If you want to enable gccgo go ahead, but
please do not create  virtual/go. Gccgo should only be used in special
cases, for example bootstrapping dev-lang/go.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-11-04 23:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 17:17 [gentoo-dev] [PATCH v1] enable gccgo for all platform Leno Hou
2015-11-02 17:30 ` William Hubbs
2015-11-02 20:12 ` Justin Lecher (jlec)
2015-11-02 22:38   ` William Hubbs
2015-11-03  2:40     ` Leno Hou
2015-11-03  7:45     ` Justin (jlec)
2015-11-03 14:56       ` William Hubbs
2015-11-03 15:09         ` James Le Cuirot
2015-11-04 23:46           ` William Hubbs [this message]
2015-11-04  2:41       ` Leno Hou
2015-11-03 20:35 ` Zac Medico
2015-11-15  8:34 ` [gentoo-dev] " Ryan Hill
2015-12-21 22:52 ` [gentoo-dev] " William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151104234629.GA21846@whubbs1.ad.gaikai.biz \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=jlec@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox