Preventing bugs with register usage and ABI compliance in hand-written assembly

[Astigeevich, Evgeny]

Hi Vicente,

Yes, you are right.
Thanks a lot for noticing the incorrect address.
Sorry for the issue.

-Evgeny

From: Vicente Romero <vicente.romero at oracle.com>
Date: Wednesday, 22 May 2024 at 22:07
To: "Astigeevich, Evgeny" <eastig at amazon.co.uk>, "compiler-dev at openjdk.org" <compiler-dev at openjdk.org>
Subject: RE: [EXTERNAL] Preventing bugs with register usage and ABI compliance in hand-written assembly


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.


Hi Evgeny,

I think you intended to post to: hotspot-compiler-dev at openjdk.org<mailto:hotspot-compiler-dev at openjdk.org>

Thanks,
Vicente
On 5/22/24 16:59, Astigeevich, Evgeny wrote:
Hello,

I’d like to discuss what options we have to prevent bugs like  https://bugs.openjdk.org/browse/JDK-8324874 “AArch64: crypto pmull based CRC32/CRC32C intrinsics clobber V8-V15 registers”.

I am thinking about something like:

“
{
    ABIVerifier abi_verifier(masm);
    …
    Some assembly code
} // When we leave the block abi_verifier will check ABI compliance
“

An alternative way might to enable ABI verification via StubCodeMark.

Kind regrads,
Evgeny Astigeevich



Amazon Development Centre (London) Ltd.Registered in England and Wales with registration number 04543232 with its registered office at 1 Principal Place, Worship Street, London EC2A 2FA, United Kingdom.





Amazon Development Centre (London) Ltd. Registered in England and Wales with registration number 04543232 with its registered office at 1 Principal Place, Worship Street, London EC2A 2FA, United Kingdom.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/compiler-dev/attachments/20240522/ea667880/attachment.htm>