cmd/compile: non-symmetric inline cost when using named vs non-named returns #38419
Labels
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Code: https://play.golang.org/p/bM-akhk0QXG
go build -gcflags "-m=2"
What did you expect to see?
NewTriangleInline
is equivalent toNewTriangleNoInline
, the only difference is that the first uses a named return and the second one doesn´t, therefore I would expect that both have the same inline cost.What did you see instead?
The text was updated successfully, but these errors were encountered: