[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

From: Ian Lance Taylor
Subject: Re: GCC's -fsplit-stack disturbing Mach's vm_allocate
Date: Sat, 22 Jun 2013 08:15:46 -0700

On Sat, Jun 22, 2013 at 12:19 AM, Thomas Schwinge
<thomas@codesourcery.com> wrote:
> On Fri, 21 Jun 2013 16:16:55 -0700 (PDT), Roland McGrath 
> <roland@hack.frob.com> wrote:
>> Split-stack is fundamentally incompatible with __hurd_threadvar_location et
> Not fundamentally: if split-stack were properly integrated into glibc,
> our threadvar resolver could track back split-stack's initial_sp (where
> the threadvars live, I presume).  But as split-stack is not generally
> implemented but currently only for x86 GNU/Linux, I suppose there's no
> real harm for GCC Go's usability when not having it implemented on x86
> GNU/Hurd -- Ian?

Go can work without split stack.  In that case libgo will use much
larger stacks for goroutines, to reduce the chance of running out of
stack space (see StackMin in libgo/runtime/proc.c).  So the number of
simultaneous goroutines that can be run will be limited.  This is
usually OK on x86_64 but it does hamper Go programs running on 32-bit


reply via email to

[Prev in Thread] Current Thread [Next in Thread]