Re:Hunting Down a Go Runtime Bug on 32-Bit Embedded Systems
by ReactiveJelly on Saturday August 29, 2026 @09:47AM
(#49489888)
So a stronger type system in the boundary between Go and Linux would have caught this?
[ Parent
| on HN ]
Re:Hunting Down a Go Runtime Bug on 32-Bit Embedded Systems
by fn-mote on Saturday August 29, 2026 @10:03AM
(#49489988)
My reading is that this is entirely Go’s fault. In Go, there was a union of two different types without metadata to distinguish the two. The disambiguation was done by looking to see if the data looked like a certain pointer.
I think the reason it is a problem only in 32 bit systems is that the assignment setting the lower half of the data is a 32 bit op, which can overflow the 16 bits used, but won’t affect the other half of a 64 bit value. (Corrections welcome.)