On Fri, 21 Apr 2023 02:33:37 GMT, SUN Guoyun wrote:
>> Matias Saavedra Silva has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> s390x NULL to nullptr
>
> src/hotspot/cpu/riscv/templateTable_riscv.cpp line 2233:
>
>> 2231:
>> 2232: __ lo
On Tue, 28 Mar 2023 19:50:36 GMT, Matias Saavedra Silva
wrote:
>> The current structure used to store the resolution information for
>> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
>> ambigious fields f1 and f2. This structure can hold information for fields,
>>
On Mon, 3 Apr 2023 05:57:18 GMT, Thomas Stuefe wrote:
> > I wonder about the explicit exclusion of arm. Every other CPU seems to be
> > taken care of, even those Oracle does not maintain. Just curious, was there
> > a special reason for excluding arm?
>
> There is no special reason ARM32 was e
On Fri, 31 Mar 2023 15:34:12 GMT, Matias Saavedra Silva
wrote:
> > This obviously breaks arm, since its implementation is missing. I opened
> > https://bugs.openjdk.org/browse/JDK-8305387 to track this. This is
> > unfortunate since it holds work on arm in other areas, in my case for
> > #109
On Tue, 28 Mar 2023 19:50:36 GMT, Matias Saavedra Silva
wrote:
>> The current structure used to store the resolution information for
>> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
>> ambigious fields f1 and f2. This structure can hold information for fields,
>>
On Tue, 28 Mar 2023 19:50:36 GMT, Matias Saavedra Silva
wrote:
>> The current structure used to store the resolution information for
>> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
>> ambigious fields f1 and f2. This structure can hold information for fields,
>>
On Tue, 28 Mar 2023 19:50:36 GMT, Matias Saavedra Silva
wrote:
>> The current structure used to store the resolution information for
>> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
>> ambigious fields f1 and f2. This structure can hold information for fields,
>>
> The current structure used to store the resolution information for
> invokedynamic, ConstantPoolCacheEntry, is difficult to interpret due to its
> ambigious fields f1 and f2. This structure can hold information for fields,
> methods, and invokedynamics and each of its fields can hold different
