You can have a look at
pacman-key --list-keys 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
That should list the alhp buildbot key.
Yep, this is a know issue. I already experimented with separating the builds on a network level via systemd-nspawn. There is only firewall integration left, otherwise this already worked in my…
Just FYI, all builds after 2022-05-12 01:00 UTC are build with the new flags -mpclmul and -devirtualize-at-ltrans.
We probably could test it, but I would prefer not doing it on the production machine. I can probably make some test builds locally later/tomorrow.
This should not happen anymore with https://git.harting.dev/ALHP/ALHP.GO/commit/f190902b412df4bffee6c553fbd179a67557cb02 now in place. I'll leave this open unitl linux-zen is rebuild.
What do you think about '-fipa-pta'? It does take more memory but is commonly used on Gentoo builds.
Do you got some headroom on the build server in terms of memory? :)
Not really…
I do not know how, but gitea somehow fucked up rebasing the branch before merging, so I had to cherry pick your commit. Consider this merged.
This is probably a side-effect of -O3 and can be safely ignored.
LTo is handled mostly by upstream now. Not sure about -target-cpu, but at least -opt-level seems to be set corecctly with out current flag configuration.
I indentified the underlying problem. I requeued linux-zen for now.
Hi @RubenKelevra,
good idea, why not. I think we can integrate this (commented out) in a new mirror release. Comment can include a link to either this issue or the guide you linked, with a hint…
@anonfunc well,
-fdevirtualize-speculativelywasn't mentioned here before, but it sounds like it could lead to further optimisations down the road :)So maybe just add it to the ToDo…