Arch Linux ALHP Adds x86-64-v4 Repository For Packages Built With AVX-512

[phoronix]

Phoronix: Arch Linux ALHP Adds x86-64-v4 Repository For Packages Built With AVX-512

The unofficial "ALHP" repositories for Arch Linux have begun offering an x86-64-v4 tuned repository for packages built against this current highest x86-64 micro-architecture feature level for the latest Intel and AMD processors with AVX-512 support...

https://www.phoronix.com/news/Arch-Linux-ALHP-x86-64-v4

[ptr1337]

We also provide them since a while:

https://cachyos.org/blog/x86-64-v4-testing/

edit: I wonder anyways, why you don't really have us on track in any x86-64-x news.

[Kjell]

CachyOS had this for a long time. It's my favorite distro/package repository by far in Arch Linux.

Wish they would team up with Artix Linux to provide optimized binaries for SystemD-free installations like Dinit!

[V1tol]

The only problem with these 3rd party repos is that they are additive and can't replace default Arch ones. And often you have a situation when half of your software is x86-64-v3-pgo-lto-wtf, and half of it came from Arch repos just because there newer packages were built. And you receive weird problems because of this (like broken screen sharing in browsers because libpipewire breaks with LTO). I wish Arch provide full x86-64-v3 repo themselves.

[ms178]

Let's wait and see if x86-64-v4 will stay alive, there is talk on the GCC mailing list to abandon it alltogether due to obstacles with AVX10 on the road going forward: https://gcc.gnu.org/pipermail/gcc-pa...er/640327.html

By the way, someone subscribed to the GCC ML should notice them that x86-64-v4 is a convenient and compatible way to use AVX-512 on existing CPU implementations distribution-wide. And I doubt there is much willingness on the distribution side to make that Zen 4-only going forward if x86-64-v4 died.

[Sethox]

The only problem with these 3rd party repos is that they are additive and can't replace default Arch ones. And often you have a situation when half of your software is x86-64-v3-pgo-lto-wtf, and half of it came from Arch repos just because there newer packages were built. And you receive weird problems because of this (like broken screen sharing in browsers because libpipewire breaks with LTO). I wish Arch provide full x86-64-v3 repo themselves.

You just described why third-party has issues while looking over the fact that this is the next best thing to appliance. Tests and research (gathering data) has to be made before it naturally flows in the official repos.

[ms178]

The only problem with these 3rd party repos is that they are additive and can't replace default Arch ones. And often you have a situation when half of your software is x86-64-v3-pgo-lto-wtf, and half of it came from Arch repos just because there newer packages were built. And you receive weird problems because of this (like broken screen sharing in browsers because libpipewire breaks with LTO). I wish Arch provide full x86-64-v3 repo themselves.

Yeah, the way Arch handles this needs a lot of care while updating and in maintenance if you have a lot of custom-compiled packages. CachyOS is better in this regard if you stick to their repos because they aim to keep their packages better in-sync with upstream and try to minimize breakage across their repos. ALHP had some issues in the past due to their slow build server, important distro-wide packages e.g. python, took way too long to incorporate and the delay caused breakage when updating from the standard Arch repo in the meantime.

[Phil995511]

The day they finally integrate Calamares (which is elsewhere has just been released in version 3.3) so maybe I will be interested by Arch Linux.

[SofS]

Anyone here knows the subset of AVX512 that x86-64-v4 enables? It seems to be "AVX512F, AVX512BW, AVX512CD, AVX512DQ, AVX512VL", but where is the detailed documentation? The closest I was able to find is https://gcc.gnu.org/onlinedocs/gcc/x...Functions.html

[Kjell]

The only problem with these 3rd party repos is that they are additive and can't replace default Arch ones. And often you have a situation when half of your software is x86-64-v3-pgo-lto-wtf, and half of it came from Arch repos just because there newer packages were built. And you receive weird problems because of this (like broken screen sharing in browsers because libpipewire breaks with LTO). I wish Arch provide full x86-64-v3 repo themselves.

This happens often in ALHP
Never had such issue after switching to CachyOS