> > There is some overhead when using gccgo, because of the need to > interact with the Go scheduler. The overhead should be slightly less. >
Any idea what (very rough is fine) that overhead is when compared to the standard go toolchain? -- 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. For more options, visit https://groups.google.com/d/optout.
