On Sat, Oct 1, 2016 at 5:23 AM, web user <webuser1...@gmail.com> wrote: > On a side not. The functions I call will from c into go will be called very > frequently and the overhead of a callback from c might become an issue. I've > heard that overhead can be as high as 200ns. Couple of questions: > > 1. Is the overhead not there when using gccgo?
There is some overhead when using gccgo, because of the need to interact with the Go scheduler. The overhead should be slightly less. > 2. What is the current state of gccgo support? Does it fully support 1.7 on > linux? The current development branch of gccgo fully supports 1.7. However, that is not in any GCC release, due to the different release timing between GCC releases and Go releases. If you build GCC yourself from tip, you will get a version of gccgo with full 1.7 support. > 3. Would the command that I currently use: > > go build -buildmode c-archive -o libgolang.a > > be the same on gccgo? Yes. 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. For more options, visit https://groups.google.com/d/optout.
