<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 27/02/2023 11:04, George Adams
wrote:<br>
</div>
<blockquote type="cite" cite="mid:VI1PR83MB039873A31D5C151FFE31343888AF9@VI1PR83MB0398.EURPRD83.prod.outlook.com">
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
Hi all,</p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
I’ve been asked to socialize my proposed JEP to
deprecate the Windows x86-32 port on this mailing list.</p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
A link to the draft JEP can be found here:<span class="Apple-converted-space"> </span><a href="https://bugs.openjdk.org/browse/JDK-8303167" style="color:rgb(0,120,212);
text-decoration:underline" moz-do-not-send="true" class="moz-txt-link-freetext">https://bugs.openjdk.org/browse/JDK-8303167</a></p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="MsoNormal" style="color:rgb(33,33,33);
margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif; line-height:1.5">
In summary, the main motivation for this JEP is that
there is currently no implementation of <a href="https://openjdk.org/jeps/436" target="_blank" title="Follow link" style="color:rgb(0,120,212);
text-decoration:underline" moz-do-not-send="true">JEP
436 (Virtual Threads)</a> for 32-bit platforms and
without a vendor stepping forward to implement this it's
unlikely that OpenJDK will be able to continue
supporting 32-bit architectures. Another motivation is
that Windows 10 (the last Windows operating system to
support a 32-bit installation) will reach EOL<span class="Apple-converted-space"> </span><span dir="ltr" style="color:currentcolor; text-decoration:underline;
font-size:inherit!important;
text-decoration-color:rgb(0,120,212)!important"><span dir="ltr" style="text-decoration-color:rgb(0,120,212)!important">on
October 14</span></span>, 20251.</p>
<br>
</div>
</div>
</div>
</div>
</blockquote>
When you build JDK 19+ to target windows-x86 then it will use an
alternative implementation of virtual thread that creates a kernel
thread for each virtual thread. So it doesn't scale but it's good
enough for Zero and ports that are a bit behind.<br>
<br>
That said, it's a good topic to bring up. I don't expect dropping
windows-x86 will remove the burden of keeping the x86_32 port
working, to do that would require dropping linux-x86 too. So maybe
the discussion should be broadened to ask if the time is approaching
to remove the x86_32 port? At one point, one of the arguments to
keep linux-x86 working was reconditioning older computers but I
don't know if this is still the case. I see a mail to jdk-dev from
Mark Yagnatinsky that talks about JNI libs or drivers that are
32-bit only. There isn't much context but it would be surprising for
something that is actively maintained to not have a 64-bit build in
2023. He also mentions limiting resources but that may be a case
where an OS container should be used. It might be that you expand
the Motivation in draft JEP to cover these points.<br>
<br>
-Alan<br>
<br>
</body>
</html>