Again, should the problems on other arches be different bugs?
These tests are also better with a newer package and kernel:
=== go tests ===
Running target unix
FAIL: go.test/test/ken/cplx2.go execution, -O2 -g
FAIL: go.test/test/peano.go execution, -O2 -g
=== go Summary for unix ===
# of expected passes 5053
# of unexpected failures 2
# of expected failures 1
# of untested testcases 6
Running target unix/-fstack-protector
FAIL: go.test/test/ken/cplx2.go execution, -O2 -g
FAIL: go.test/test/peano.go execution, -O2 -g
=== go Summary for unix/-fstack-protector ===
# of expected passes 5053
# of unexpected failures 2
# of expected failures 1
# of untested testcases 6
=== go Summary ===
# of expected passes 10106
# of unexpected failures 4
# of expected failures 2
# of untested testcases 12
/home/mwhudson/gcc-4.8-4.8.2/build/gcc/testsuite/go/../../gccgo version 4.8.2
(Ubuntu/Linaro 4.8.2-10ubuntu2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256283
Title:
go tests failing on AArch64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1256283/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
