[go-nuts] Re: Profiling the `go` tool itself?

Tentatively, most of the slowdown was caused by the eCryptFS layer (encrypted $HOME). But it probably means Go does too many FS syscalls, since Rust was tenfold faster. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this gr

Re: [go-nuts] Profiling the `go` tool itself?

> On Wed, Oct 2, 2024 at 10:11 AM opennota wrote: > > > > Cold-start builds are slow af on my machine (think tens of minutes), and > have been like that since around Go 1.20. (See also maybe related > https://github.com/golang/go/issues/38939). Is there a way to profile `g

[go-nuts] Profiling the `go` tool itself?

Cold-start builds are slow af on my machine (think tens of minutes), and have been like that since around Go 1.20. (See also maybe related https://github.com/golang/go/issues/38939). Is there a way to profile `go build` to determine why it takes it so long to build even a simple hello-world pro

Re: [go-nuts] Is there any way to force Go to call asm function using register-based arguments?

Ok Google, so one can use `-asmflags=-compiling-runtime` to work around this limitation. The resulting speed-up can be well worth it. On Saturday, 1 July 2023 at 22:46:03 UTC+7 opennota wrote: Any update on this? I wanted to use the register-based calling convention as well and got &quo

Re: [go-nuts] Is there any way to force Go to call asm function using register-based arguments?

Any update on this? I wanted to use the register-based calling convention as well and got "ABI selector only permitted when compiling runtime", too. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receivin