alice

> -DWITH_ALTIVEC=OFF -DWITH_POWER8=OFF -DWITH_POWER9=ON this breaks them again like originally so, i guess it's not altivec, but either something power9 specific, or gcc is broken for power9 the gcc in...

fails with 12.2 based gcc the same way

it could be either some UB in any ppc-specific code that gets hit by the optimiser in newer gccs only, or gcc itself above some version broke for some ppc...

applying https://github.com/zlib-ng/zlib-ng/commit/e5ab5890a89860a7f4115fca9b0fc7c778b26ef1 to 2.1.2 still seems to have the same failures

a naive usage: ```diff --- a/libarchive/archive_read_support_filter_xz.c +++ b/libarchive/archive_read_support_filter_xz.c @@ -511,11 +511,23 @@ xz_lzma_bidder_init(struct archive_read_filter *self) state->in_stream = 1; /* Initialize compression library. */ - if (self->code == ARCHIVE_FILTER_XZ) + if...

originally it was [ignored for i3 compat](https://github.com/swaywm/sway/pull/194), then in https://github.com/swaywm/sway/pull/6639 it was implemented for real, i'd guess the docs were forgotten at the time

- discord/brave/electron/... all crash due to gpu driver issues. sadly i can't tell you why or how to fix those - the journalctl oom-killer crashes you see are due to...

`glxinfo` and `eglinfo` should list `radeonsi` (the driver) in the output somewhere, and `glxgears` should work to show you some gears (from `mesa-demos`/`mesa-utils`)

ah right, you posted eglinfo already. yeah the driver is present there..

ah, i forgot that chromium is still most likely depending on that. that explains all of those cases at least someone would have to tell the chromium developers about it