[Bug go/64005] make check FAIL: sync

2015-01-18 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005 Uroš Bizjak changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug go/64005] make check FAIL: sync

2014-12-23 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005 --- Comment #3 from Uroš Bizjak --- Ian explained in an offline communication: It's more likely that with -O2 some dead pointers appears in a stack frame, and cause the garbage collector to think that the values are still live, and therefore the

[Bug go/64005] make check FAIL: sync

2014-11-20 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005 --- Comment #2 from Uroš Bizjak --- When tracing the execution after the pool_test.go:81 breakpoint, the difference between alphaev68-linux-gnu vs and x86_64-linux-gnu starts at the end of: runfinq (dummy=) at /home/uros/gcc-svn/trunk/libgo/runt

[Bug go/64005] make check FAIL: sync

2014-11-20 Thread ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005 Uroš Bizjak changed: What|Removed |Added CC||ro at CeBiTec dot Uni-Bielefeld.DE --- Co