20 ms·

This comes up a lot with my work on compiling the Linux kernel with LLVM. So much so I've made a tier list to describe what I picture as a Venn diagram of suppo

This comes up a lot with my work on compiling the Linux kernel with LLVM. So much so I've made a tier list to describe what I picture as a Venn diagram of support: https://clangbuiltlinux.github.io/ https://clangbuiltlinux.github.io/ Also recently seen on this topic: https://people.gnome.org/~federico/blog/librsvg-rust-and-non-mainstream-architectures.html https://people.gnome.org/~federico/blog/librsvg-rust-and-non... https://www.reddit.com/r/rust/comments/lfysy9/pythons_cryptography_package_introduced_build/gmq9vi8/ https://www.reddit.com/r/rust/comments/lfysy9/pythons_crypto...

eqvinox 6y ago
Does the "powerpc" listed really mean "ppc64le" and the "s390" really mean "s390x"? Certainly feels like it, but I'm not sure... If you're already making such a nice overview, could you maybe not mar it with such ambiguity? Kinda defeats the purpose :( [Ed.: even "x86" is confusing. x86_64 does work, right?]
- ndesaulniers 6y ago
  No. The kernel doesn't make such distinctions. The convention used is what the kernel sources call them under arch/. See arm64 vs aarch64 for example.
  - eqvinox 6y ago
    I guess that means that overview is for kernel developers. Those directory names are meaningless to me as an user... FWIW, I'm actually asking out of a real need. I have two powerpc boxes (no, not ppc64le) here, which we use for testing big-endian compatibility. But last I checked, LLVM supported neither 32-bit PowerPC nor big-endian PowerPC. Actually... I guess the real argument is that the kernel directory names aren't sufficient. Because they specify architecture families, not architectures. [And, funnily enough, LLVM does actually seem to support 32-bit BE PowerPC. Now I'm really confused.]
    - ndesaulniers 6y ago
      > But last I checked, LLVM supported neither 32-bit PowerPC nor big-endian PowerPC. How long ago did you check? I've been working on this for 3-4 years, and we've had coverage of kernel builds for 32b BE ppc for at least 2 years. I just checked our coverage, looks like we test ppc64, ppc64le, and ppc (32b BE). So no coverage of 32b LE atm, but I think llvm recently gained support for the relevant triple. Try it and let us know if it boots!

eqvinox 6y ago

Does the "powerpc" listed really mean "ppc64le" and the "s390" really mean "s390x"? Certainly feels like it, but I'm not sure... If you're already making such a nice overview, could you maybe not mar it with such ambiguity? Kinda defeats the purpose :( [Ed.: even "x86" is confusing. x86_64 does work, right?]

ndesaulniers 6y ago
No. The kernel doesn't make such distinctions. The convention used is what the kernel sources call them under arch/. See arm64 vs aarch64 for example.
- eqvinox 6y ago
  I guess that means that overview is for kernel developers. Those directory names are meaningless to me as an user... FWIW, I'm actually asking out of a real need. I have two powerpc boxes (no, not ppc64le) here, which we use for testing big-endian compatibility. But last I checked, LLVM supported neither 32-bit PowerPC nor big-endian PowerPC. Actually... I guess the real argument is that the kernel directory names aren't sufficient. Because they specify architecture families, not architectures. [And, funnily enough, LLVM does actually seem to support 32-bit BE PowerPC. Now I'm really confused.]
  - ndesaulniers 6y ago
    > But last I checked, LLVM supported neither 32-bit PowerPC nor big-endian PowerPC. How long ago did you check? I've been working on this for 3-4 years, and we've had coverage of kernel builds for 32b BE ppc for at least 2 years. I just checked our coverage, looks like we test ppc64, ppc64le, and ppc (32b BE). So no coverage of 32b LE atm, but I think llvm recently gained support for the relevant triple. Try it and let us know if it boots!