If you want preemption within a particular package, you can compile it "go build -gcflags=particular_package=-d=ssa/insert_resched_checks/on" . That will not fix any problems with underlying raciness, though it may mask them.
If you want an entire compiler that defaults to that mode and libraries also built that way, "GOEXPERIMENT=preemptibleloops ./make.bash" . This can slow code down quite a bit. We're not super-excited about this approach, but a fix that doesn't trash performance is tricky (we've been working on it for a while). When we do get it done right, the flags and the experiment are likely to go away. On Saturday, August 17, 2019 at 12:24:58 AM UTC-4, xkw...@connect.hku.hk wrote: > > Could you let me know which compiler can support pre-emption and how to > enable it? Thanks. > > On Saturday, August 17, 2019 at 9:20:07 AM UTC+8, Ian Davis wrote: >> >> On Fri, 16 Aug 2019, at 7:09 PM, dr.ch...@gmail.com wrote: >> >> Dear Community and dear Go-developers, >> >> Meanwhile it is clear why things do not work: >> The Go-Scheduler is unable to allow to switch to another goroutine in >> busy-waiting-loops - >> the only possibility to get around that problem is either to put >> "switch-steps" into the source >> - either "time.Sleep(1)" or "runtime.Gosched()". >> I think that THIS SHOULD BE DOCUMENTED IN THE LANGUAGE SPECIFICATION !!!!! >> >> >> I don't believe this is a language issue. Different compiler >> implementations could support pre-emption if they chose to. >> >> Ian >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a735e0bb-f2a6-4dcc-a041-48357569f379%40googlegroups.com.
