Re: Committed Go frontend

2010-12-03 Thread Ian Lance Taylor
Michael Matz writes: >> > Indeed, as of r167408, --enable-languages=all includes go. >> >> Well, yeah. Isn't that exactly what should happen? > > The precedent would be Ada. It is not included in =all, you explicitely > have to enable it via e.g. =all,ada . I would have thought Go to behave

Re: Committed Go frontend

2010-12-03 Thread Ian Lance Taylor
"Joseph S. Myers" writes: > I don't see a ChangeLog file in the gcc/go directory - I take it one will > be created for all future changes to that directory outside of the > gofrontend subdirectory? Yes, and in fact already done as of a few minutes ago. Ian

Re: Committed Go frontend

2010-12-03 Thread Ian Lance Taylor
Miles Bader writes: > Ian Lance Taylor writes: >> As I just mentioned on the gcc-patches mailing list, I have just >> committed the Go frontend to mainline. > > What's the name of the resulting compiler binary? "ggo"? gccgo. Ian

Re: Committed Go frontend

2010-12-03 Thread Joseph S. Myers
I don't see a ChangeLog file in the gcc/go directory - I take it one will be created for all future changes to that directory outside of the gofrontend subdirectory? -- Joseph S. Myers jos...@codesourcery.com

Re: Committed Go frontend

2010-12-03 Thread Michael Matz
Hi, On Fri, 3 Dec 2010, Ian Lance Taylor wrote: > Joern Rennecke writes: > > > Quoting Andrew Pinski : > > > >> On Thu, Dec 2, 2010 at 8:41 PM, Ian Lance Taylor wrote: > >>> The Go language is not built by default, so this should not have a > >>> significant effect on most developers. > >> > >

Re: Committed Go frontend

2010-12-03 Thread Joseph S. Myers
I notice two files in the front end have '#include "ansidecl.h"'. ansidecl.h is automatically included from config.h so it is not conventional for files in GCC to include it directly. -- Joseph S. Myers jos...@codesourcery.com

Re: Committed Go frontend

2010-12-03 Thread Ian Lance Taylor
Joern Rennecke writes: > Quoting Andrew Pinski : > >> On Thu, Dec 2, 2010 at 8:41 PM, Ian Lance Taylor wrote: >>> The Go language is not built by default, so this should not have a >>> significant effect on most developers. >> >> Hmm, but it looks like it is currently. > > Indeed, as of r167408,

Re: Committed Go frontend

2010-12-03 Thread Miles Bader
Ian Lance Taylor writes: > As I just mentioned on the gcc-patches mailing list, I have just > committed the Go frontend to mainline. What's the name of the resulting compiler binary? "ggo"? -Miles -- Opposition, n. In politics the party that prevents the Goverment from running amok by hamstri

Re: Committed Go frontend

2010-12-02 Thread Joern Rennecke
Quoting Andrew Pinski : On Thu, Dec 2, 2010 at 8:41 PM, Ian Lance Taylor wrote: The Go language is not built by default, so this should not have a significant effect on most developers. Hmm, but it looks like it is currently. Indeed, as of r167408, --enable-languages=all includes go.

Re: Committed Go frontend

2010-12-02 Thread Andrew Pinski
On Thu, Dec 2, 2010 at 8:41 PM, Ian Lance Taylor wrote: > The Go language is not built by default, so this should not have a > significant effect on most developers. Hmm, but it looks like it is currently. Or at least that is how I understand to read the build failure at http://gcc.gnu.org/ml/gc

Committed Go frontend

2010-12-02 Thread Ian Lance Taylor
As I just mentioned on the gcc-patches mailing list, I have just committed the Go frontend to mainline. I expect that I will use the gccgo branch going forward as a set of tested sources for generating Go code. In the next few days I will complete the final items on the frontend checklist at http