This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Discussion about merging Go frontend
- From: Ian Lance Taylor <iant at google dot com>
- To: Jack Howarth <howarth at bromo dot med dot uc dot edu>
- Cc: Dave Korn <dave dot korn dot cygwin at gmail dot com>, Andi Kleen <andi at firstfloor dot org>, Andrew Pinski <pinskia at gmail dot com>, Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Fri, 29 Oct 2010 06:49:51 -0700
- Subject: Re: Discussion about merging Go frontend
- References: <mcr7hh8qhb5.fsf@google.com> <4CC45302.9000702@gmail.com> <mcrhbgbyoef.fsf@google.com> <4CC59F1E.7040505@codesourcery.com> <mcrbp6ixhny.fsf@google.com> <AANLkTikEy7ER+CkQdWo0XHPoBORvbp8JZ226QFM68PZv@mail.gmail.com> <87pquy3yh5.fsf@basil.nowhere.org> <4CC60C5E.6050605@gmail.com> <mcr1v79bx8q.fsf@google.com> <4CCA8C22.8030308@gmail.com> <20101029131853.GA25158@bromo.med.uc.edu>
Jack Howarth <howarth@bromo.med.uc.edu> writes:
> Doesn't the go compiler require functional split stack support? Mike Stump
> left me with the impression that split stack support would require additional
> linker support on darwin.
The Go compiler can work without split stack support. The effect is
that you are limited in the number of goroutines you can create,
particularly on a 32-bit system. And you are also limited in the depth
of recursion and size of local variables you can create. But you can
write working Go programs.
The objfile patch, however, is not really about Go, although gccgo will
use it. It's really about LTO. If it works for LTO, it will work for
gccgo.
Ian