News for hackers. Stuff that matters.
Re:Do Not Use Go for 32bit Development by doug363 on Sunday April 08, 2012 @10:40PM (#3815615)
But the reason why there is an explicit flag in the first place is that there's a lot of code out there that doesn't work with pointers >= 0x80000000, or when pointers could differ by more than that. Things like pointer "tagging", and signed integer overflow bugs, are examples of the sort of code that can be affected. Without knowing details about the Go code generation and runtime/garbage collection, it would be a bit risky to just set the flag and hope for the best.
Re:Do Not Use Go for 32bit Development by barrkel on Sunday April 08, 2012 @11:55PM (#3815769)
Oh, I know; I've written bounds-checking logic for RTLs that use casts to integers and tests for negativity to check for overrun, implicitly assuming 31-bit address space. My only point is that a limitation of the Go linker does not preclude setting the flag.
Re:Do Not Use Go for 32bit Development by 4ad on Monday April 09, 2012 @06:43AM (#3816421)
No such problems in Go. I just checked and the flag is set by default in all Windows binaries.