RFR:8166684:implement intrinsic code with vector instructions for Unsafe.copyMemory()

[Doerr, Martin]

Hi Michihiro,

the initialization of tmp1 should be done outside of the loop. Beside that, the change looks good:
http://cr.openjdk.java.net/~mdoerr/8166684_PPC64_unsafe_copymemory/webrev.00/

Best regards,
Martin


From: Michihiro Horie [mailto:HORIE at jp.ibm.com]
Sent: Montag, 26. September 2016 09:37
To: Doerr, Martin <martin.doerr at sap.com>; Simonis, Volker <volker.simonis at sap.com>; ppc-aix-port-dev at openjdk.java.net
Cc: volker.simonis at gmail.com; Gustavo Romero <gromero at linux.vnet.ibm.com>; Hiroshi H Horii <HORII at jp.ibm.com>
Subject: RFR:8166684:implement intrinsic code with vector instructions for Unsafe.copyMemory()


Dear all,

Could I please request reviews for the following change?
This change was created for JDK9.

I added fixes to the intrinsic code for sun.misc.Unsafe.copyMemory() by using VSX.
Since Spark often invokes Unsafe.copyMemory(), it is beneficial to use the vector instructions for these intrinsic code.

jira: https://bugs.openjdk.java.net/browse/JDK-8166684
diff: (See attached file: unsafe-copymemory-openjdk9.diff)

Best regards,
--
Michihiro Horie,
IBM Research - Tokyo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/ppc-aix-port-dev/attachments/20160926/20df9b66/attachment.html>