<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div style="font-family: inherit; font-size: inherit; color: rgb(0, 0, 0);"></div>
<div style="font-family: inherit; font-size: inherit; color: rgb(0, 0, 0);">I absolutely agree with all your comments. To the point of deprecating the Linux x86 port at the same time, I think this is a great idea but felt it would be most appropriate for this
to be raised in a separate JEP. When I spoke to several vendors recently they all felt that it was the right time to do this but I’d rather have someone else step forward and propose the Linux x86 deprecation separately.</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Alan Bateman <Alan.Bateman@oracle.com><br>
<b>Sent:</b> 27 February 2023 19:15<br>
<b>To:</b> George Adams <George.Adams@microsoft.com>; jdk-dev@openjdk.java.net <jdk-dev@openjdk.java.net><br>
<b>Subject:</b> [EXTERNAL] Re: Proposed JEP - Deprecate the Windows x86-32 Port</font>
<div> </div>
</div>
<div><br>
<br>
<div class="x_moz-cite-prefix">On 27/02/2023 11:04, George Adams wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<p class="x_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="x_MsoNormal" style="color:rgb(33,33,33); margin:0cm; font-size:11pt; font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="x_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="x_MsoNormal" style="color:rgb(33,33,33); margin:0cm; font-size:11pt; font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="x_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="x_Apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.openjdk.org%2Fbrowse%2FJDK-8303167&data=05%7C01%7CGeorge.Adams%40microsoft.com%7C47da7314d0eb4b35565c08db18f70a76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638131221569762154%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cn8MKpwdseIHN%2Bbo0f2la8QLmOx51Xv9r7wn7e9AjNc%3D&reserved=0" originalsrc="https://bugs.openjdk.org/browse/JDK-8303167" shash="Pama3RcW3HcB0d+dhl9gJJ6CoAwiNVlaejtOtgdo9SEgUAqX1FRaaLgL6PXo9gvKmxLsuF1tgYElPIIjN/Sh8pT6MMwXUSY9zowt7wCOGLcHcpzg0+McYgyyYaRE89t7s2dF8jE6Hj2Xb81YYAc+jaPum9s6N/9iD3AtVsSk9z8=" class="x_moz-txt-link-freetext" style="color:rgb(0,120,212); text-decoration:underline">https://bugs.openjdk.org/browse/JDK-8303167</a></p>
<p class="x_MsoNormal" style="color:rgb(33,33,33); margin:0cm; font-size:11pt; font-family:Calibri,sans-serif; line-height:1.5">
</p>
<p class="x_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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.org%2Fjeps%2F436&data=05%7C01%7CGeorge.Adams%40microsoft.com%7C47da7314d0eb4b35565c08db18f70a76%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638131221569918383%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RodxRRngviyDQagvLObc8brMW0obrQenU2uq4%2BS7A04%3D&reserved=0" originalsrc="https://openjdk.org/jeps/436" shash="z/GEbOl1n0N1UEeeEV9eQdKfDC5yeVwWiU14gqfI2LlCuyPvD8odDOoVcxcvwC+5BFghRRJvfgsUuRAEQd77VUqFlEcNYOHqcaTMT1C4NkVfj6a+JtRdyZGnD9RXiwOc3nKKnQr0cH42MPA+ORvBBOuJIJY3MR4duX+PkMGvnNo=" target="_blank" title="Follow link" style="color:rgb(0,120,212); text-decoration:underline">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="x_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>
</div>
</body>
</html>