RFR: 8282392: [zero] Build broken on AArch64 [v2]

[Aleksey Shipilev]

On Mon, 28 Feb 2022 16:39:48 GMT, Andrew Haley <aph at openjdk.org> wrote:

> That's what we looked at and it was more of a mess, IMO. In the end it's a judgment call which to have, and I've seen this kind of mistake, where a particular port is confused with a particular CPU, enough times that I think this is OK; YMMV.

>From the perspective of Zero maintenance, having the Zero-specific workarounds explicitly doing `!ZERO` is cleaner. This mess is mostly Zero-s problem with idenitifying itself as CPU. So, in my mind, there is little reason to accommodate that problem with "port" defines.

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

PR: https://git.openjdk.java.net/jdk/pull/7633