Open tuxillo opened 1 year ago
As witnessed by CI, other BSD systems (FreeBSD, OpenBSD, NetBSD) do not seem to have this issue. Do you know what makes DragonFly BSD peculiar in this aspect? Is it possible to add a CI job?
We just don't support AVX512. It's still to be implemented.
PR is welcome, ideally accompanied by a CI job for DragonFly BSD, otherwise it can easily regress back in future.
Sure, I'll send one when I have some time. Can you point me to the other BSD CI jobs?
Thanks. Looks like I'd have to send a PR to pg-vm-images first.
I am not sure whether other OSes will be affected by this issue but it seems the declaration of COMPILER_SUPPORTS_AVX512 alone might not be enough?
Would it be better to say the definition of COMPILER_SUPPORTS_AVX512 needs to be extended to account for Dragonfly? It's already mixing checks of compiler version and operating system version, anyway, which makes the variable's name look misleading to me.
While building ghc-9.4.6 under DragonFly BSD we got a strange haddock crash:
After some investigation, it seems the issue is that DragonFly BSD does not support AVX512. So changing the ifdef here:
https://github.com/haskell/text/blob/master/cbits/measure_off.c#L214
To avoid going through the avx512 path solved the issue and the build finished ok.
I am not sure whether other OSes will be affected by this issue but it seems the declaration of
COMPILER_SUPPORTS_AVX512
alone might not be enough?