Yes, the author of that post is also me : )
在 2017年1月9日星期一 UTC+8下午6:30:59，Konstantin Khomoutov写道：
>
> On Sun, 8 Jan 2017 01:22:59 -0800 (PST)
> 陈诚 > wrote:
>
> > Is the size of a pointer value 32 bits or 64 bits in golang when
> > build with `GOARCH=amd64` option specified and running on 64-bit
On Sun, 8 Jan 2017 01:22:59 -0800 (PST)
陈诚 wrote:
> Is the size of a pointer value 32 bits or 64 bits in golang when
> build with `GOARCH=amd64` option specified and running on 64-bit OS?
[...]
Isn't it http://stackoverflow.com/q/41531337/720999 ?
--
You received this message because you are s
What you are talking about is called a torn write, which can occur if a value
is written to memory but not aligned properly as the processor or memory
subsystem must convert this write into two to correct for the miss alignment.
Most processors that I know of, and all the ones that Go supports,
Is the size of a pointer value 32 bits or 64 bits in golang when build with
`GOARCH=amd64` option specified and running on 64-bit OS?
If it's 64-bit size, is a global pointer value 8-byte aligned in memory so
that a read or write operation of that pointer value is carried out
atomically?
For exa
