On 2022-09-16 19:42, Mark Millard wrote:
Mark Millard escreveu no dia sábado, 10/09/2022
à(s) 12:53:
Daniel Engberg wrote on
Date: Sat, 10 Sep 2022 09:45:21 UTC :
Since there is work and general interest regarding optimization
would
it
make sense to make LTO and possibly CODEGEN_UNITS=1 op
> Mark Millard escreveu no dia sábado, 10/09/2022
> à(s) 12:53:
>
>> Daniel Engberg wrote on
>> Date: Sat, 10 Sep 2022 09:45:21 UTC :
>>
>>> Since there is work and general interest regarding optimization would
>>> it
>>> make sense to make LTO and possibly CODEGEN_UNITS=1 opt-out while we
>>
On 2022-09-13 11:54, Nuno Teixeira wrote:
Hi,
I think this issue is related to what happened in terms of
optimizations in go 1.18.3_1: ---
Add amd64 microarchitecture level knobs for the Go compiler. Note that
this will affect only the compiler itself, port users will still need
to
set GO
Hi,
I think this issue is related to what happened in terms of optimizations in
go 1.18.3_1:
---
Add amd64 microarchitecture level knobs for the Go compiler. Note that
this will affect only the compiler itself, port users will still need to
set GOAMD64 in the environment to adjust the microarchite
Daniel Engberg wrote on
Date: Sat, 10 Sep 2022 09:45:21 UTC :
> Since there is work and general interest regarding optimization would it
> make sense to make LTO and possibly CODEGEN_UNITS=1 opt-out while we
> still have a fairly manageable amount of ports using Rust?
Just making sure I under
Hi,
Since there is work and general interest regarding optimization would it
make sense to make LTO and possibly CODEGEN_UNITS=1 opt-out while we
still have a fairly manageable amount of ports using Rust?
Just an idea I got from looking at
https://git.alpinelinux.org/aports/tree/testing/b3su
