Change powerpc64 base CPU

[sanxiyn]

Currently, following targets use “ppc64” as base CPU: powerpc64-unknown-linux-gnu, powerpc64-unknown-linux-musl, powerpc64-unknown-freebsd.

In LLVM, “ppc64” implies “+altivec”. This is unfortunate, because it means Rust targets are unusable on devices based on PowerPC e5500, which is fairly popular. In particular, #43610 is about QorIQ P5040 SoC using PowerPC e5500 core, and #59040 is about QorIQ T1042 SoC using PowerPC e5500 core.

Thoughts?

[cuviper]

I think it would make sense to have a new std-only target for this, similar to how we have i586 for those who can't use i686 for lack of SSE2.

[gnzlbg]

The proposed change is only for the big-endian targets right? That is, the pp64le targets would still be compiled with altivec enabled right ?

[sanxiyn]

Yes, I am not proposing to change powerpc64le targets.

[gnzlbg]

Then this sounds good to me 👍

[nagisa]

I would be fine with disabling altivec by default on both ppc64, because it is easier to enable it back for new binaries than to disable it for already-built ones.

Removing I-nominated, because T-compiler don’t have stakeholders in PPC support to the best of my knowledge, so it is impossible for us to arrive at a meaningful decision.

[gnzlbg]

@nagisa is there a group for packagers / distros contributors ? I think this would interest them, since the ppc targets are being shipped for some linux distros.

[cuviper]

I would be fine with disabling altivec by default on both ppc64

By "both", do you mean ppc64le too? AFAIK little-endian only became a viable Linux target starting with POWER8, which definitely has Altivec. LLVM also defines the ppc64le CPU as POWER8.

because it is easier to enable it back for new binaries than to disable it for already-built ones.

It's easy to add features for your own code, but std is stuck at the baseline unless you xargo it.

[nagisa]

By "both", do you mean ppc64le too?

Yes. Then again, if ppc64le without altivec cannot possibly exist, then the lowest common denominator is good as well. Knowing PPC, though, you can run most of the chips in either endianess.

It's easy to add features for your own code, but std is stuck at the baseline unless you xargo it.

On one hand you’re right, on the other most of std is so generic, that in practice most of the code will end up using whatever features that are enabled for the final artifact. I guess #38913 cannot come soon enough.

[cuviper]

Knowing PPC, though, you can run most of the chips in either endianess.

I don't know the full details, but this IBM FAQ says:

Which POWER processors support little endian mode?

The POWER8 processor is the first processor to support little endian and big endian modes equivalently. Although previous generations of the POWER processors had basic little endian functionality, they did not fully implement the necessary instructions in such a way to enable enterprise operating system offerings.

[awilfox]

Personally over here at Adélie we only ship BE PPC64, and we enable AltiVec in all of our packages. We may, in the future, offer a separate target for non-AltiVec PPC64 machines. I would definitely support Rust targeting more types of POWER, and I know the FreeBSD people specifically support the e5500s.

As an aside: IBM's really unreliable for endian questions. You can run BE on any generation of POWER, and you can run LE on most generations of POWER. You can even run accelerated LE in KVM on the Power Mac G5, though the firmware itself prevents bare metal LE mode. Not that I really recommend that; BE mode is faster, better, and easier to debug (biased opinion, of course).

[gnzlbg]

@lu-zero correctly pointed out that we currently do also enable VSX for ppc64le.