On Mon, 4 Dec 2023 14:58:34 GMT, Jorn Vernee wrote:
>> src/java.base/share/classes/java/lang/invoke/X-VarHandleByteArrayView.java.template
>> line 594:
>>
>>> 592: @ForceInline
>>> 593: static int indexRO(ByteBuffer bb, int index) {
>>> 594: if (bb.isReadOnly())
>>
On Mon, 4 Dec 2023 14:49:39 GMT, Jorn Vernee wrote:
>> Chen Liang has updated the pull request with a new target base due to a
>> merge or a rebase. The pull request now contains two commits:
>>
>> - Merge branch 'master' of https://github.com/openjdk/jdk into
>> cleanup/vh-template-share
>>
On Mon, 6 Nov 2023 08:19:19 GMT, Chen Liang wrote:
>> VarHandle implementations have many static fields and methods that can be
>> pulled to the common superclass to avoid repeated initialization and code
>> duplication.
>>
>> In addition, the Unsafe-based Buffer field access are replaced by u
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
On Sun, 24 Sep 2023 13:16:02 GMT, Chen Liang wrote:
>> VarHandle implementations have many static fields and methods that can be
>> pulled to the common superclass to avoid repeated initialization and code
>> duplication.
>>
>> In addition, the Unsafe-based Buffer field access are replaced by
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
On Sun, 24 Sep 2023 02:11:50 GMT, Chen Liang wrote:
>> VarHandle implementations have many static fields and methods that can be
>> pulled to the common superclass to avoid repeated initialization and code
>> duplication.
>>
>> In addition, the Unsafe-based Buffer field access are replaced by
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
On Thu, 21 Sep 2023 08:50:00 GMT, Chen Liang wrote:
>> VarHandle implementations have many static fields and methods that can be
>> pulled to the common superclass to avoid repeated initialization and code
>> duplication.
>>
>> In addition, the Unsafe-based Buffer field access are replaced by
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
On Thu, 21 Sep 2023 08:50:00 GMT, Chen Liang wrote:
>> VarHandle implementations have many static fields and methods that can be
>> pulled to the common superclass to avoid repeated initialization and code
>> duplication.
>>
>> In addition, the Unsafe-based Buffer field access are replaced by
> VarHandle implementations have many static fields and methods that can be
> pulled to the common superclass to avoid repeated initialization and code
> duplication.
>
> In addition, the Unsafe-based Buffer field access are replaced by usage of
> public methods or JavaNioAccess.
Chen Liang ha
VarHandle implementations have many static fields and methods that can be
pulled to the common superclass to avoid repeated initialization and code
duplication.
In addition, the Unsafe-based Buffer field access are replaced by usage of
public methods or JavaNioAccess.
-
Commit mes
15 matches
Mail list logo
