> According to https://golang.org/cl/18200, this change broke Go on PPC64le.
Any other platform where this also happened? > I haven't investigated myself and I don't know why. Go does not use > stack trampolines for function closures. It does use function > closures, but they are built on the heap. It also uses closures > mediated by libffi. The Go frontend does not enable custom function > descriptors. There are a couple of changes to the RTL expander for calls; they are supposed to be transparent but they might have tripped on a latent issue. > It should be possible to recreate the problem by configuring with > --enable-languages=go and running `make > RUNTESTFLAGS="go-test.exp=recover.go" check-gcc-go`. Thanks, I'll try to reproduce tomorrow. -- Eric Botcazou
