Hi all,
I use Visual Studio 2022 (17.0.4) on WSL 1 Ubuntu to build OpenJDK for
Windows on Windows 11.
I sometimes saw Internal Error in masm as following:
```
Assembling:
c:\github-forked\jdk\src\jdk.incubator.vector\windows\native\libjsvml\jsvml_d_cos_windows_x86.S
MASM : fatal error A101
On Sat, 18 Dec 2021 00:40:05 GMT, David Holmes wrote:
> I think specifying "allow" would be the behaviour preserving change here.
This is strictly true. I did think about doing this. However, I don't think it
makes much of a practical difference. It's always been fully supported to
enable the
On Fri, 17 Dec 2021 20:01:27 GMT, Stuart Marks wrote:
> Enable the security manager in rmiregistry's launcher arguments.
My concern is that having the SM installed during part of VM initialization
could lead to different behaviour compared to installing the SM after that.
This may be a small r
On Fri, 17 Dec 2021 20:01:27 GMT, Stuart Marks wrote:
> Enable the security manager in rmiregistry's launcher arguments.
As things stand, `rmiregsitry -J-Djava.security.manager` and `rmiregistry
-J-Djava.security.manager=allow` are equivalent because rmiregistry sets the
default SM. Some diffe
