RFR: 8332724: x86 MacroAssembler may over-align code [v3]

[Daniel Jeliński]

On Thu, 23 May 2024 18:15:27 GMT, Daniel Jeliński <djelinski at openjdk.org> wrote:

>> The methods align32 and align64 are supposed to align the next instruction to the next 32 or 64 byte boundary using the minimum number of NOP bytes. However, when the target represented as a 32bit signed int is negative, the instructions generate 32 or 64 NOP bytes too many. This was observed in `jbyte_disjoint_arraycopy_avx3` on a Linux machine, where a single align32 invocation generated 63 bytes of NOPs.
>> 
>> This PR addresses the problem by using bit operations to calculate the required number of bytes.
>> 
>> Tier1-3 tests passed.
>> 
>> On a side note, `align64` and `align32` instructions were meant for aligning data for use with zmm / ymm loads, but nowadays they are frequently used in places where `align(CodeEntryAlignment)` or `align(OptoLoopAlignment)` would be more appropriate. I can address that in a separate PR if you think it's worth fixing.
>
> Daniel Jeliński has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Fix 32-bit compilation

Thanks for the reviews. Unless someone objects, I'll integrate this later today.

Re revisiting flag types, it seems that the only options currently available are bool, int, intx and uintx, other types might [make jvmci unhappy](https://github.com/openjdk/jdk/blob/af056c1676dab3b0b35666a8259db60f9bbf824e/src/hotspot/share/jvmci/jvmciCompilerToVMInit.cpp#L294).

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

PR Comment: https://git.openjdk.org/jdk/pull/19353#issuecomment-2128769210