There is also a command-line proof-of-concept that combines it with
profiling information to show you only the missed/unabled optimizations
that are also hot spots in the profile.
https://github.com/dr2chase/gc-lsp-tools
There's a lot of checks and things that can't be optimized away, but very
fe
And gopls will compute them as diagnostics. For instance, if using vscode
and gopls, then in setting.json:
"gopls": {
"codelens": {
"gc_details": true,
}
}
and a clickable 'Toggle gc annotation details' should appear just above the
package statement.
On Fri, Sep 4, 2020 at 4:28 PM Ian Lan
[ + drchase ]
On Fri, Sep 4, 2020 at 1:16 PM Falco Wockenfuß wrote:
>
> sorry if this is a dumb question, but the Release Notes for go 1.15 have the
> Note:
> The compiler's -json optimization logging now reports large (>= 128 byte)
> copies and includes explanations of escape analysis decision
Hi,
sorry if this is a dumb question, but the Release Notes for go 1.15 have
the Note:
The compiler's -json optimization logging now reports large (>= 128 byte)
copies and includes explanations of escape analysis decisions.
But I didn't find anything about "-json" as a flag for go build or sim
