[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GCC's -fsplit-stack disturbing Mach's vm_allocate
From: |
Samuel Thibault |
Subject: |
Re: GCC's -fsplit-stack disturbing Mach's vm_allocate |
Date: |
Fri, 4 Apr 2014 21:14:16 +0200 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Hello,
Thomas Schwinge, le Wed 26 Jun 2013 23:30:03 +0200, a écrit :
> On Sat, 22 Jun 2013 08:15:46 -0700, Ian Lance Taylor <iant@google.com> wrote:
> > 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
> > x86.
>
> OK, but that's not the most pressing issue we're having right now.
> Anyway, as it stands, the split-stack code doesn't work on Hurd, so I
> disabled it in r200434 as follows:
Maybe you'd want to re-enable it, now that we have got rid of threadvars :)
Samuel
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate,
Samuel Thibault <=
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate, Svante Signell, 2014/04/09
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate, Samuel Thibault, 2014/04/16
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate, Samuel Thibault, 2014/04/18
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate, Svante Signell, 2014/04/24
- Re: GCC's -fsplit-stack disturbing Mach's vm_allocate, Justus Winter, 2014/04/26