https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005
Uroš Bizjak ubizjak at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005
--- Comment #3 from Uroš Bizjak ubizjak at gmail dot com ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005
Uroš Bizjak ubizjak at gmail dot com changed:
What|Removed |Added
CC||ro at CeBiTec dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64005
--- Comment #2 from Uroš Bizjak ubizjak at gmail dot com ---
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=optimized out)
