Re: [jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used [v2]

2020-12-14 Thread Claes Redestad
On Mon, 14 Dec 2020 18:07:14 GMT, Maurizio Cimadamore wrote: >> This patch fixes a problem with type profile pollution when segments of >> different kinds are used on the same memory access var handle, or on the >> same `MemoryAccess` static method. >> >> In principle, argument profiling shou

Re: [jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used [v2]

2020-12-14 Thread Maurizio Cimadamore
> This patch fixes a problem with type profile pollution when segments of > different kinds are used on the same memory access var handle, or on the same > `MemoryAccess` static method. > > In principle, argument profiling should kick in for VarHandles and > MethodHandles, and that should be en

Re: RFR: 8253368: TLS connection always receives close_notify exception

2020-12-14 Thread Xue-Lei Andrew Fan
On Fri, 13 Nov 2020 14:16:35 GMT, Sean Coffey wrote: > removing the "closing inbound before receiving peer's close_notify" exception > that can be seen with TLS stack if calling close on inbound. After reading > the relevant parts of the TLS v1.2/v1.3 RFCs, I believe the local end point > does

Re: [jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used

2020-12-14 Thread Maurizio Cimadamore
On Mon, 14 Dec 2020 15:48:07 GMT, Claes Redestad wrote: >> This patch fixes a problem with type profile pollution when segments of >> different kinds are used on the same memory access var handle, or on the >> same `MemoryAccess` static method. >> >> In principle, argument profiling should kic

Re: [jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used

2020-12-14 Thread Claes Redestad
On Mon, 14 Dec 2020 14:46:41 GMT, Maurizio Cimadamore wrote: > This patch fixes a problem with type profile pollution when segments of > different kinds are used on the same memory access var handle, or on the same > `MemoryAccess` static method. > > In principle, argument profiling should ki

Re: [jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used

2020-12-14 Thread Vladimir Ivanov
On Mon, 14 Dec 2020 14:46:41 GMT, Maurizio Cimadamore wrote: > This patch fixes a problem with type profile pollution when segments of > different kinds are used on the same memory access var handle, or on the same > `MemoryAccess` static method. > > In principle, argument profiling should ki

[jdk16] RFR: 8258242: Type profile pollution occurs when memory segments of different kinds are used

2020-12-14 Thread Maurizio Cimadamore
This patch fixes a problem with type profile pollution when segments of different kinds are used on the same memory access var handle, or on the same `MemoryAccess` static method. In principle, argument profiling should kick in for VarHandles and MethodHandles, and that should be enough at leas