Example where gccgo is 4 times faster than go build

I posted code for an example where gccgo produces an executable that is 4 times faster than the same code compiled with go build using the gc compiler at

As there has not been an effective suggestion at a user-level how to fix this, I thought it might be something the developers would be interested in looking at. The reason for this post is to encourage anyone on the development side of Go to look into what’s happening to create such a performance difference between binaries created by the two compilers…