Cool, thanks!
Do you know anyone who could sponsor this and create a web-review against the
patch?
Regards,
Sergeyt Tsypanov
13.08.2020, 19:22, "Sean Mullan" :
> On 8/13/20 9:04 AM, Сергей Цыпанов wrote:
>> Hi,
>>
>> I don't have account in JBS, so I cannot file an issue.
>>
>> Previously wh
On 8/13/20 9:04 AM, Сергей Цыпанов wrote:
Hi,
I don't have account in JBS, so I cannot file an issue.
Previously when I submitted patches via core-libs-dev mailing list previleged
users
filed the issues and created web-reviews.
I think this should be a subtask of
https://bugs.openjdk.java.ne
Hi,
I don't have account in JBS, so I cannot file an issue.
Previously when I submitted patches via core-libs-dev mailing list previleged
users
filed the issues and created web-reviews.
I think this should be a subtask of
https://bugs.openjdk.java.net/browse/JDK-6736490, there's
already one I
On 8/13/20 7:04 AM, Сергей Цыпанов wrote:
Hello,
previously I've sent an email regarding removal of redundant assignments if
default values to volatile fields, see
https://mail.openjdk.java.net/pipermail/security-dev/2020-June/022137.html
There was a concern whether it's completely safe to rem
Hello,
previously I've sent an email regarding removal of redundant assignments if
default values to volatile fields, see
https://mail.openjdk.java.net/pipermail/security-dev/2020-June/022137.html
There was a concern whether it's completely safe to remove those assignments
from JMM point of vie
Hello,
while investigating an issue I've found out that assignment of default value to
volatile fields slows down object instantiation.
Consider the benchmark:
@State(Scope.Thread)
@OutputTimeUnit(TimeUnit.NANOSECONDS)
@BenchmarkMode(value = Mode.AverageTime)
@Fork(jvmArgsAppend = {"-Xms2g", "-
