On Tue, 27 Jul 2021 02:52:13 GMT, Eric Liu wrote:
>> @sviswa7, SLP flow will either have a constant 8bit shift value or a
>> variable shift present in vector, this also include broadcasted non-constant
>> shift value or a shift value beyond 8 bit.
>
> It would be better comment here, since the
On Tue, 27 Jul 2021 01:54:01 GMT, Sandhya Viswanathan
wrote:
>> Jatin Bhateja has updated the pull request with a new target base due to a
>> merge or a rebase. The pull request now contains 19 commits:
>>
>> - 8266054: Re-designing benchmark to remove noise.
>> - Merge branch 'master' of
On 28/07/2021 12:17 am, Thomas Stuefe wrote:
On Mon, 26 Jul 2021 21:08:04 GMT, David Holmes wrote:
Before looking at this, have you checked the startup performance impact?
Thanks,
David
-
Hi David,
performance should not be a problem. The potentially costly thing is the
underlying
On Tue, 27 Apr 2021 17:56:04 GMT, Jatin Bhateja wrote:
> Current VectorAPI Java side implementation expresses rotateLeft and
> rotateRight operation using following operations:-
>
> vec1 = lanewise(VectorOperators.LSHL, n)
> vec2 = lanewise(VectorOperators.LSHR, n)
> res =
On Tue, 27 Jul 2021 00:24:52 GMT, Sandhya Viswanathan
wrote:
>> Jatin Bhateja has updated the pull request with a new target base due to a
>> merge or a rebase. The pull request now contains 19 commits:
>>
>> - 8266054: Re-designing benchmark to remove noise.
>> - Merge branch 'master' of
On Fri, 23 Jul 2021 12:32:04 GMT, Severin Gehwolf wrote:
> > Could this be some setting configured on your box that is picked up as an
> > additional limit ?
>
> Possibly. Not sure where to look, though.
I ask some local experts about that issue.
What do you think about accepting, when
On Mon, 26 Jul 2021 21:08:04 GMT, David Holmes wrote:
> Before looking at this, have you checked the startup performance impact?
>
> Thanks,
> David
> -
Hi David,
performance should not be a problem. The potentially costly thing is the
underlying hashmap. But we keep it operating with a
> Greetings,
>
> Object.finalize() was deprecated in JDK9. There is an ongoing effort to
> replace and mitigate Object.finalize() uses in the JDK libraries; please see
> https://bugs.openjdk.java.net/browse/JDK-8253568 for more information.
>
> We also like to assist users in replacing and
> Greetings,
>
> Object.finalize() was deprecated in JDK9. There is an ongoing effort to
> replace and mitigate Object.finalize() uses in the JDK libraries; please see
> https://bugs.openjdk.java.net/browse/JDK-8253568 for more information.
>
> We also like to assist users in replacing and
On Fri, 23 Jul 2021 18:03:31 GMT, Sergey Chernyshev
wrote:
> Dear colleagues,
>
> Please review the patch that replaces the lambdas with anonymous classes
> which solves the startup time regression as shown below.
>
> I attached the Bytestacks flamegraphs for both original (regression) and
> Greetings,
>
> Object.finalize() was deprecated in JDK9. There is an ongoing effort to
> replace and mitigate Object.finalize() uses in the JDK libraries; please see
> https://bugs.openjdk.java.net/browse/JDK-8253568 for more information.
>
> We also like to assist users in replacing and
On Mon, 26 Jul 2021 21:07:59 GMT, Lance Andersen wrote:
> I have not gone through the latest update in detail but there are some
> changes that are needed. Before moving forward with the CSR, I would like to
> give time for additional feedback on naming and design.
This proposal will need a
On Tue, 27 Jul 2021 08:17:55 GMT, Jatin Bhateja wrote:
>> src/hotspot/share/opto/vectorIntrinsics.cpp line 1598:
>>
>>> 1596: cnt = elem_bt == T_LONG ? gvn().transform(new ConvI2LNode(cnt))
>>> : cnt;
>>> 1597: opd2 = gvn().transform(VectorNode::scalar2vector(cnt, num_elem,
>>>
Hello,
I know I am a bit late, but just wanted to mention, that since finding
finalizers with Bytecode analysis is doable (and probably easier to deal with
such scan reports), I don’t see much value in a JFR event, especially
considering it even has native code executed. (Not so sure about
On Tue, 20 Jul 2021 09:57:07 GMT, Jatin Bhateja wrote:
>> Current VectorAPI Java side implementation expresses rotateLeft and
>> rotateRight operation using following operations:-
>>
>> vec1 = lanewise(VectorOperators.LSHL, n)
>> vec2 = lanewise(VectorOperators.LSHR, n)
>> res =
On Tue, 27 Jul 2021 18:05:49 GMT, Sandhya Viswanathan
wrote:
>> Correcting this, I2L may be needed in auto-vectorization flow since
>> Integer/Long.rotate[Right/Left] APIs accept only integral shift, so for
>> Long.rotate* operations integral shift value must be converted to long using
>>
On Tue, 20 Jul 2021 09:57:07 GMT, Jatin Bhateja wrote:
>> Current VectorAPI Java side implementation expresses rotateLeft and
>> rotateRight operation using following operations:-
>>
>> vec1 = lanewise(VectorOperators.LSHL, n)
>> vec2 = lanewise(VectorOperators.LSHR, n)
>> res =
On Tue, 27 Jul 2021 18:31:20 GMT, Sandhya Viswanathan
wrote:
>> Jatin Bhateja has updated the pull request with a new target base due to a
>> merge or a rebase. The pull request now contains 19 commits:
>>
>> - 8266054: Re-designing benchmark to remove noise.
>> - Merge branch 'master' of
Backout the following changes due to vector tests failures in tier 2 and later:
[JDK-8266054](https://bugs.openjdk.java.net/browse/JDK-8266054) VectorAPI
rotate operation optimization
Changes also caused copyright header validation failure in Tier1 due to missing
`,` after copyright year in
On Wed, 28 Jul 2021 05:35:59 GMT, Vladimir Kozlov wrote:
> Backout the following changes due to vector tests failures in tier 2 and
> later:
> [JDK-8266054](https://bugs.openjdk.java.net/browse/JDK-8266054) VectorAPI
> rotate operation optimization
>
> Changes also caused copyright header
20 matches
Mail list logo
