[jdk18] RFR: 8278267: ARM32: several vector test failures for ASHR [v2]
Hao Sun
haosun at openjdk.java.net
Fri Dec 24 01:48:19 UTC 2021
On Fri, 24 Dec 2021 01:34:50 GMT, Hao Sun <haosun at openjdk.org> wrote:
>> In ARM32, "VSHL (register)" instruction [1] is shared by vector left
>> shift and vector right shift, and the condition to distinguish them is
>> whether the shift count value is positve or negative. Hence, negation
>> operation is needed before conducting vector right shift.
>>
>> For vector right shift, the shift count can be a RShiftCntV or a normal
>> vector node. Take test case Byte64VectorTests.java [2][3] as an example.
>> Note that RShiftCntV is already negated via rules "vsrcntD" and
>> "vsrcntX" whereas the normal vector node is NOT, since we don't know
>> whether a normal vector node is used as a vector shift count or not.
>> This is the root cause for these vector test failures.
>>
>> The fix is simple, moving the negation from "vsrcntD|X" to the
>> corresponding vector right shift rules.
>>
>> Affected rules are vsrlBB_reg and vsraBB_reg. Note that vector shift
>> related rules are in form of "vsAABB_CC", where
>> 1) AA can be l (left shift), rl (logical right shift) and ra (arithmetic
>> right shift).
>> 2) BB can be 8B/16B (byte type), 4S/8S (short type), 2I/4I (int type)
>> and 2L (long type).
>> 3) CC can be reg (register case) and immI (immediate case).
>>
>> Minor updates:
>> 1) Merge "vslcntD" and "vsrcntD" into rule "vscntD", as these two rules
>> conduct the same duplication operation now.
>> 2) Update the "match" primitive for vsraBB_immI rules.
>> 3) Style issue: remove the surrounding space for "ins_pipe" primitive.
>>
>> Tests:
>> We ran tier 1~3 tests on ARM32 platform. With this patch, previously
>> failed vector test cases can pass now without introducing test
>> regression.
>>
>> [1] https://developer.arm.com/documentation/ddi0406/c/Application-Level-Architecture/Instruction-Details/Alphabetical-list-of-instructions/VSHL--register-?lang=en
>> [2] https://github.com/openjdk/jdk/blame/master/test/jdk/jdk/incubator/vector/Byte64VectorTests.java#L2237
>> [3] https://github.com/openjdk/jdk/blame/master/test/jdk/jdk/incubator/vector/Byte64VectorTests.java#L2425
>
> Hao Sun has updated the pull request incrementally with one additional commit since the last revision:
>
> Use is_var_shift() to determmine the location of negation use for right shifts
>
> Method is_var_shift() denotes that vector shift count is a variable
> shift:
> 1) for this case, vector shift count should be negated before conducting
> right shifts. E.g., vsrl4S_reg_var rule.
> 2) for the opposite case, vector shift count is generated via RShiftCntV
> rules and is already negated there. Hence, no negation is needed.
> E.g., vsrl4S_reg rule.
>
> Besides, it's safe to add "hash()" and "cmp()" methods for ShiftV node.
Tests on the latest code:
We ran tier 1~3 tests on linux+ARM32 platform. With this patch, previously failed vector test cases can pass now without introducing test regression.
-------------
PR: https://git.openjdk.java.net/jdk18/pull/41
More information about the hotspot-compiler-dev
mailing list