RFR (S) 8175370: Fix C calling convention for CRC32C and Adler32 intrinsics

Schmidt, Lutz lutz.schmidt at sap.com
Fri Feb 24 10:05:17 UTC 2017

Hi all,

I would like to request to put all activities re this RFR on hold. As per private communication with Goetz, this fix should not be necessary. On the other hand, my prepared CRC32C contribution, despite almost identical to CRC32, does not run without it.

I am looking for that needle… Sorry for the confusion!

Regards, Lutz

From: hotspot-compiler-dev <hotspot-compiler-dev-bounces at openjdk.java.net> on behalf of Lutz Schmidt <lutz.schmidt at sap.com>
Date: Donnerstag, 23. Februar 2017 um 10:26
To: "hotspot-compiler-dev at openjdk.java.net" <hotspot-compiler-dev at openjdk.java.net>
Subject: RFR (S) 8175370: Fix C calling convention for CRC32C and Adler32 intrinsics

Hi all,

may I kindly request reviews for my small bug fix? Further down the road, I would need a sponsor, too.

Bug: https://bugs.openjdk.java.net/browse/JDK-8175370
Webrev: http://cr.openjdk.java.net/~lucy/webrevs/8175370/

On some platforms (ppc, s390) the C calling convention requires “int” arguments to be converted to “long” by the caller. This requirement was not observed by c2-generated calls to the CRC32C and Adler32 intrinsics. The fix was rather simple, using the calls from the CRC32 intrinsics as a template.

This is not an issue as of now. The affected intrinsics are not yet (but will soon be) implemented. You may see this as a preemptive bug fix.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20170224/9d8fb5e9/attachment.html>

More information about the hotspot-compiler-dev mailing list