This is the mail archive of the gcc-patches@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: Go patch committed: Multiplex goroutines onto OS threads

From: Paolo Bonzini <bonzini at gnu dot org>
To: gcc-patches at gcc dot gnu dot org
Date: Wed, 14 Dec 2011 17:32:04 +0100
Subject: Re: Go patch committed: Multiplex goroutines onto OS threads
References: <mcr1uss6bpn.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <4EE8B206.3020000@gnu.org> <mcrhb13qjto.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <4EE8BEEA.2020503@gnu.org> <mcrvcpjp370.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <4EE8C509.2000603@gnu.org> <mcrmxavp2by.fsf@dhcp-172-18-216-180.mtv.corp.google.com>

On 12/14/2011 05:04 PM, Ian Lance Taylor wrote:

>  The OpenBSD thread runtime.  It's similar to old LinuxThreads, but
>  with only 1 kernel thread per process IIUC.

Oh, hmmm, that might be a problem.

The other Go compiler seems to use the rfork system call to create new
threads, passing RFPROC | RFTHREAD | RFMEM | RFNOWAIT.

Yeah, found it now... it implements basically its own thread runtime. But it only has spinlocks right now.

Paolo

References:
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Paolo Bonzini
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Ian Lance Taylor
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Paolo Bonzini
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Ian Lance Taylor
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Paolo Bonzini
- Re: Go patch committed: Multiplex goroutines onto OS threads
  - From: Ian Lance Taylor

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