Re: [go-nuts] Register-based ABI benchmarks

2022-02-04 Thread Didier Spezia
Thank you - it makes sense. The first time I read https://github.com/golang/go/blob/master/src/cmd/compile/abi-internal.md I thought there were plenty of registers for parameters, even for x86_64. But with string, slices, interfaces, etc ... multiple registers are used, so it does not take so man

Re: [go-nuts] Register-based ABI benchmarks

2022-02-03 Thread Robert Engels
+1. Sometimes the compiler optimizations are even worse if they change the behavior the chip was typically expecting. > On Feb 3, 2022, at 2:23 PM, Ian Lance Taylor wrote: > > On Thu, Feb 3, 2022 at 7:21 AM Didier Spezia wrote: >> >> It seems Aarch64 benefits more from the register-based AB

Re: [go-nuts] Register-based ABI benchmarks

2022-02-03 Thread Ian Lance Taylor
On Thu, Feb 3, 2022 at 7:21 AM Didier Spezia wrote: > > It seems Aarch64 benefits more from the register-based ABI than x86_64. > I don''t see really why. Does anyone have a clue? My view is that the x86 architecture has fewer registers and has had a massive decades-long investment in performance

Re: [go-nuts] Register-based ABI benchmarks

2022-02-03 Thread Robert Engels
Usually Arm cpus have a lot more registers to pass values in. > On Feb 3, 2022, at 9:21 AM, Didier Spezia wrote: > > We are using our own benchmark to evaluate the performance of different CPU > models of cloud providers. > https://github.com/AmadeusITGroup/cpubench1A > > One point we have r

[go-nuts] Register-based ABI benchmarks

2022-02-03 Thread Didier Spezia
We are using our own benchmark to evaluate the performance of different CPU models of cloud providers. https://github.com/AmadeusITGroup/cpubench1A One point we have realized is the results of such benchmark can be biased depending on the version of the Go compiler. For instance, the register-