Comment 4 for bug 1256281

These failures are all quite interesting.

----------------------------------------------------------------------------
--- FAIL: TestLog2 (0.00 seconds)
        all_test.go:2281: Log2(1) = 4.756597398230631e-17, want 0
        all_test.go:2288: Log2(2**0) = 4.756597398230631e-17, want 0
FAIL
FAIL: math
----------------------------------------------------------------------------

That certainly looks worrying!

----------------------------------------------------------------------------
runtime: memory allocated by OS (0x2012c3e000) not in usable range [0x8500000,0x88500000)
runtime: out of memory: cannot allocate 2097152-byte block (536870912 in use)
fatal error: out of memory

goroutine 114 [running]:
runtime_dopanic
        ../../../src/libgo/runtime/panic.c:71
runtime_throw
        ../../../src/libgo/runtime/panic.c:106
runtime_mallocgc
        ../../../src/libgo/runtime/malloc.goc:83
runtime_malg
        ../../../src/libgo/runtime/proc.c:1910
__go_go
        ../../../src/libgo/runtime/proc.c:1965
net.TestDialTimeoutFDLeak
        /home/mwhudson/gcc-4.8-4.8.2/build/aarch64-linux-gnu/libgo/gotest29428/test/dial_test.go:276
testing.tRunner
        ../../../src/libgo/go/testing/testing.go:353
kickoff
        ../../../src/libgo/runtime/proc.c:229

        :0
panic during panic
FAIL: net
----------------------------------------------------------------------------

I actually know what's going on here, it's related to the reservation fixes for statically linked binaries in the latest gcc-4.8 upload. I'll try to propose a fix for this too (I got distracted with arguin^Wdiscussing the fix with go core devs)

----------------------------------------------------------------------------
all_test.go: In function 'reflect_test.takesEmpty':
all_test.go:1443:1: error: total size of local objects too large
 func takesEmpty(e emptyStruct) {
 ^
FAIL: reflect
----------------------------------------------------------------------------

This is the same problem as bug 1263806