On Wed, Feb 13, 2019 at 5:21 PM Ian Lance Taylor wrote:
>
> Nikhil Benesch noticed that changes in the GCC backend were making the
> use of defer functions that call recover less efficient. A defer
> thunk is a generated function that looks like this (this is the entire
> function body):
>
>
On Thu, Feb 14, 2019 at 1:41 AM Richard Biener
wrote:
>
> On Thu, Feb 14, 2019 at 2:21 AM Ian Lance Taylor wrote:
> >
> > Nikhil Benesch noticed that changes in the GCC backend were making the
> > use of defer functions that call recover less efficient. A defer
> > thunk is a generated function
On Thu, Feb 14, 2019 at 2:21 AM Ian Lance Taylor wrote:
>
> Nikhil Benesch noticed that changes in the GCC backend were making the
> use of defer functions that call recover less efficient. A defer
> thunk is a generated function that looks like this (this is the entire
> function body):
>
>
Nikhil Benesch noticed that changes in the GCC backend were making the
use of defer functions that call recover less efficient. A defer
thunk is a generated function that looks like this (this is the entire
function body):
if !runtime.setdeferretaddr(&L) {
deferredFunction()
}
L:
