PING^2 [8u] Request for enhancement backport approval for 8154156: PPC64: improve array copy stubs by using vector instructions
gromero at linux.vnet.ibm.com
Wed Jan 16 21:33:23 UTC 2019
Could somebody kindly point me out to what is missing (if anything) in
order to proceed with the approval for this backport?
This change is the first of a series of PPC64 backports planned to jdk8u,
like AES BE, SHA2, and latest CRC32 enhancements, so it's blocking
important PPC64 backports.
As Ogata pointed out, it's already reviewed by Martin from SAP on the
I understand the review from Martin is sufficient for this approval, which
On 01/15/2019 07:14 AM, Kazunori Ogata wrote:
> Ping. Can anyone approve an enhancement backport request for 8154156:
> PPC64: improve array copy stubs by using vector instructions?
> ----- Forwarded by Kazunori Ogata/Japan/IBM on 2019/01/15 18:12 -----
> Kazunori Ogata/Japan/IBM wrote on 2019/01/08 14:13:24:
>> From: Kazunori Ogata/Japan/IBM
>> To: jdk8u-dev at openjdk.java.net
>> Date: 2019/01/08 14:13
>> Subject: [8u] Request for enhancement backport approval for 8154156:
>> PPC64: improve array copy stubs by using vector instructions
>> May I get an approval for enhancement backport of 8154156: PPC64:
>> array copy stubs by using vector instructions?
>> To make this patch buildable (and usable by other planned backports
>> in ), I cherry picked config_dscr() and its dependent code from [2,3]
>> and has_mfdscr() from .
>> These changes have been reviewed in hotspot-compiler-dev ML:
>> Original patch: http://hg.openjdk.java.net/jdk/jdk/rev/c9d756fa846e
>> I confirmed it was buildable for both release and fastdebug builds, and
>> JTREG caused no degradation.
>>  8149655: PPC64: Implement CompactString intrinsics
>>  8080684: PPC64: Fix little-endian build after "8077838: Recent
>> developments for ppc"
>>  8077838: Recent developments for ppc.
More information about the jdk8u-dev