https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60406
--- Comment #22 from Dominik Vogt <vogt at linux dot vnet.ibm.com> ---
>> Hm, so the patch penalises platforms that cannot deal with the
>> 16 byte window?
> Yes, but, recall that on your system almost all tests pass using the
> code that is in the tree today, before your patch.
But they really only succeed "by accident". The call for any platform might
introduce control flow into the thunk and trigger the problem in any of the
test cases.
> The spec says "Suppose a function G defers a function D that calls
> recover and a panic occurs in a function on the same goroutine in
> which G is executing." The order is 1) G defers D; 2) a panic occurs.
> ...
I'd still not understand it that way, but from other documentation the
intention is "clear". Maybe another bullet could be added to the list
below:
"The return value of recover is nil if ...
...
* defer was called when the panic already existed"
