This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Discussion about merging Go frontend

From: Ian Lance Taylor <iant at google dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: Paolo Bonzini <bonzini at gnu dot org>, gcc at gcc dot gnu dot org
Date: Sun, 31 Oct 2010 10:53:17 -0700
Subject: Re: Discussion about merging Go frontend
References: <mcr7hh8qhb5.fsf@google.com> <4CC4A1F7.4060501@gnu.org> <mcr7hh04mma.fsf@google.com> <AANLkTim=W0FkYu2orbkKfykn+q17uGxWw980mkv+dwvj@mail.gmail.com> <mcr39ro4lho.fsf@google.com> <AANLkTi=ffRYSOuDB1uNA+X5X6E-xzW3jTJfrRthqogHn@mail.gmail.com>

"H.J. Lu" <hjl.tools@gmail.com> writes:

> Will put
>
> if [ Go is enabled ]; then
>   boot_language=yes
> fi
>
> in cp/config-lang.in work?

Probably, but why should I change cp/config-lang.in if I want to support
Go?  Everything required to support Go should, as much as possible, be
in the Go frontend.

Ian

References:
- Discussion about merging Go frontend
  - From: Ian Lance Taylor
- Re: Discussion about merging Go frontend
  - From: Paolo Bonzini
- Re: Discussion about merging Go frontend
  - From: Ian Lance Taylor
- Re: Discussion about merging Go frontend
  - From: H.J. Lu
- Re: Discussion about merging Go frontend
  - From: Ian Lance Taylor
- Re: Discussion about merging Go frontend
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]