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.]
> 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.
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.]