On Tue, Nov 6, 2012 at 10:46 AM, Ian Lance Taylor <i...@google.com> wrote: > This patch to the Go compiler and library changes the size of the Go > type "int" to be the same as the size of a pointer. This means that on > x86_64 the size of int will be 64 bits. This matches the new behaviour > of the other Go compiler, and is the intended implementation for the > future Go 1.1 release. Bootstrapped and ran Go testsuite on > x86_64-unknown-linux-gnu. Committed to mainline. > > Ian >
On x32, I saw spawn -ignore SIGHUP /export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/gcc/testsuite/go3/../../gccgo -B/export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/gcc/testsuite/go3/../../ ./tmp.go -fno-diagnostics-show-caret -I/export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/x86_64-unknown-linux-gnu/./libgo -w -O0 -g -fno-var-tracking-assignments -L/export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/x86_64-unknown-linux-gnu/./libgo -L/export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/x86_64-unknown-linux-gnu/./libgo/.libs -lm -mx32 -o /export/build/gnu/gcc-x32-mx32-native/build-x86_64-linux/gcc/testsuite/go3/tmp.x^M ./tmp.go:932:21: error: array index out of bounds^M ./tmp.go:933:23: error: array index out of bounds^M ./tmp.go:934:23: error: array index out of bounds^M ... Is this expected? -- H.J.
