https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83314
--- Comment #4 from John Paul Adrian Glaubitz <glaubitz at physik dot
fu-berlin.de> ---
Ok, I should have actually tested this on real hardware right away.
Here's on my Amiga 4000:
root@elgar:~> ./hello
5662
fatal error: memstats.heap_live not aligned to 8 bytes
goroutine 16 [running, locked to thread]:
runtime.dopanic
../../../src/libgo/go/runtime/panic.go:832
runtime.throw
../../../src/libgo/go/runtime/panic.go:758
futexwakeup addr=0xc111aa0e returned -1
fatal error: unexpected signal during runtime execution
panic during panic
[signal SIGSEGV: segmentation violation code=1 addr=4102 pc=3233247334]
futexwakeup addr=0xc111aa0e returned -1
fatal error: unexpected signal during runtime execution
stack trace unavailable
root@elgar:~>
On a sidenote: That's probably the first time Go is running on an Amiga!
