Paolo Bonzini <bonz...@gnu.org> writes: > On 12/14/2011 04:45 PM, Ian Lance Taylor wrote: >>> > - sigaltstack always returns EINVAL when using threads; >> That is odd. sigaltstack is very useful when using threads. >> >>> > - the threads are identified by the runtime from their stack pointer, >>> > so you risk confusing the runtime very much if you switch between >>> > coroutines. >> I'm not sure what this means--I'm not sure which runtime you're >> referring to here. > > 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. Ian
