RFR: 8308246: PPC64le build broken after JDK-8304913 [v2]

[Roger Riggs]

On Wed, 17 May 2023 10:31:25 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> Yes, linux-ppc64 is big endian. The 2 flavors are completely incompatible. linux-ppc64le is basically a new platform. Endianness should actually get checked in addition to the archName.
>
>> Yes, linux-ppc64 is big endian. The 2 flavors are completely incompatible. linux-ppc64le is basically a new platform. Endianness should actually get checked in addition to the archName.
> 
> Okay, I was only asking because the ModuleTarget attribute has the OS and arch, the endianness is derived from those right now. Maybe in the future there can be more about the architecture and processor features (e.g. soft vs. hard float).  So mulling over this change and wondering what happens if there is cross linking involve these two platforms.

Hmm,  most java bytecode (classfiles) aren't going to care about the endian-ness; in int is an int, etc.
Runtime calls to extract int from byte[] is going to check a runtime flag; possibly static and optimization by HotSpot, etc.
The Architecture enum was intending to capture essential build time attributes.
If there is a need for more static attributes of a build, the current API doesn't cover that.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/14027#discussion_r1196716416