Hi khanh:
I met that problem too, and I thought I somehow fix it. I located the
source code and found that when caller function is compiled with
"fsplit-stack" and callee function is compiled with "fno-split-stack", the
address of caller functions has to be relocated. However it remains me that
Hey,
It seems that structs perform faster when aligned with cache line size, but
how about when using global variables? Would it be more performant if I
used a struct to hold multiple cache values instead of global variables?
To clarify, for example:
var (
val0 int
val1 int
...
val
I've discovered a few problems with time.Time but thought I better discuss
here first before creating issues at https://github.com/golang/go/issues
(in case I missed something obvious :). These are mainly performance
issues, but there is also the serious problem that it is easy to
accidentally
