Named results allocated on stack instead of register?

[tapi...@gmail.com]

Sometimes, a function with named results is slower.

For example: https://play.golang.org/p/wvWkfSRqDLr

The generated directives are almost the same for the two

functions with a named and unnamed result, except one difference.

For the function with the named result, the result represents as "".ret

in the generated directive, but for the function with the unnamed result,

the result represents as "".~r1 in the generated directive.

Does "".ret means the result is allocated on stack?

[tapi...@gmail.com]

It looks this is related to code inlining.

If we add //go:noinline directive for the two functions,

then they have no performance difference.