<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">>
</span><span style="letter-spacing: normal; font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; font-weight: 400; color: rgb(36, 36, 36); background-color: rgb(255, 255, 255);">Although
I guess if they’re not updating to newer Windows (and hardware), they may not be upgrading Java without 32bit Windows support either.</span></div>
<div class="elementToProof"><span style="letter-spacing: normal; font-family: "DejaVu Sans", "Bitstream Vera Sans", "Luxi Sans", Verdana, Arial, Helvetica; font-size: 10pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div class="elementToProof"><span style="font-family: "DejaVu Sans", "Bitstream Vera Sans", "Luxi Sans", Verdana, Arial, Helvetica; font-size: 10pt; color: rgb(0, 0, 0);">This thinking was part of the logic behind JEP 449.</span></div>
<div class="elementToProof"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">---> "</span><span style="letter-spacing: normal; font-family: "DejaVu Sans", "Bitstream Vera Sans", "Luxi Sans", Verdana, Arial, Helvetica; font-size: 13.3333px; font-weight: 400; color: rgb(0, 0, 0);">Legacy
systems are unlikely to migrate to versions of the JDK following the release of Java 21."</span></div>
<div class="elementToProof"><span style="letter-spacing: normal; font-family: "DejaVu Sans", "Bitstream Vera Sans", "Luxi Sans", Verdana, Arial, Helvetica; font-size: 13.3333px; font-weight: 400; color: rgb(0, 0, 0);"><br>
</span></div>
<div class="elementToProof"><span style="letter-spacing: normal; font-family: "DejaVu Sans", "Bitstream Vera Sans", "Luxi Sans", Verdana, Arial, Helvetica; font-size: 13.3333px; font-weight: 400; color: rgb(0, 0, 0);">If there is a Java system still running
on an old version of Windows 32-bit -- that will by the way soon be EOL -- it is unlikely that the team will move said system to a newer version of Java.
</span><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">More often than not, there are cases of users not even running the latest minor version of older major versions
of Java (7, 8, 11).</span></div>
<div id="appendonsend"></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> jdk-dev <jdk-dev-retn@openjdk.org> on behalf of Eric Bresie <ebresie@gmail.com><br>
<b>Sent:</b> December 7, 2023 12:37 PM<br>
<b>To:</b> Magnus Ihse Bursie <magnus.ihse.bursie@oracle.com><br>
<b>Cc:</b> Stewart Addison <sxa@redhat.com>; jdk-dev@openjdk.org <jdk-dev@openjdk.org><br>
<b>Subject:</b> [EXTERNAL] Re: Windows-x86 (32-bit) build is broken. Time to retire it?</font>
<div> </div>
</div>
<div>
<table border="0" cellspacing="0" cellpadding="0" width="100%" align="left" style="border:0; display:table; width:100%; table-layout:fixed; border-collapse:seperate; float:none">
<tbody style="display:block">
<tr>
<td valign="middle" width="1px" bgcolor="#A6A6A6" cellpadding="7px 2px 7px 2px" style="padding:7px 2px 7px 2px; background-color:#A6A6A6">
</td>
<td valign="middle" width="100%" bgcolor="#EAEAEA" cellpadding="7px 5px 7px 15px" color="#212121" style="width:100%; background-color:#EAEAEA; padding:7px 5px 7px 15px; font-family:wf_segoe-ui_normal,Segoe UI,Segoe WP,Tahoma,Arial,sans-serif; font-size:12px; font-weight:normal; color:#212121; text-align:left; word-wrap:break-word">
<div>Some people who received this message don't often get email from ebresie@gmail.com.
<a href="https://aka.ms/LearnAboutSenderIdentification">Learn why this is important</a></div>
</td>
<td valign="middle" align="left" width="75px" bgcolor="#EAEAEA" cellpadding="7px 5px 7px 5px" color="#212121" style="width:75px; background-color:#EAEAEA; padding:7px 5px 7px 5px; font-family:wf_segoe-ui_normal,Segoe UI,Segoe WP,Tahoma,Arial,sans-serif; font-size:12px; font-weight:normal; color:#212121; text-align:left; word-wrap:break-word">
</td>
</tr>
</tbody>
</table>
<div>
<div dir="auto">Just curious if anyone has any visibility as to how widely 32-bit windows may still be in use? </div>
<div dir="auto">I’d imagine there could still be a lot of older systems (and maybe some embedded case) with 32bit windows still in use which the removal risks some possible bad vibes for that user base.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Although I guess if they’re not updating to newer Windows (and hardware), they may not be upgrading Java without 32bit Windows support either.<br>
</div>
<div><br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Thu, Dec 7, 2023 at 5:38 AM Magnus Ihse Bursie <<a href="mailto:magnus.ihse.bursie@oracle.com">magnus.ihse.bursie@oracle.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left-width:1px; border-left-style:solid; padding-left:1ex; border-left-color:rgb(204,204,204)">
On 2023-12-06 11:22, Stewart Addison wrote:<br>
<br>
><br>
> I think there's a discussion to be had here regarding 32-bit support <br>
> in general going forward - I have a specific question about arm32 and <br>
> whether anyone is actively maintaining that one but perhaps that's a <br>
> matter for another thread unless anyone wants to jump in and say <br>
> they'll be keeping arm32 alive in the codebase.<br>
<br>
Obviously the glory days of 32-bit support are over. But I'm guessing it <br>
will be some more time before all 32-bit code can be dropped. So I think <br>
it is important not to conflate dropping general 32-bit support with the <br>
more specific case of dropping win32. The former is more about cpu <br>
support, the latter more about os support.<br>
<br>
Arm32 in specific has never had any really active backers; it seems to <br>
be slowly dying but is apparently still on life-support. Let's keep that <br>
out of the win32 discussion.<br>
<br>
/Magnus<br>
<br>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>