<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
We don't have a issue filed for moving the cpu/x86 code to
cpu/x86_32 (say), but if you want to do it, it's not a difficult
task. All of the code there should be copied and moved, including
c1/c2 MacroAssembler code.<br>
<br>
Coleen<br>
<br>
<div class="moz-cite-prefix">On 7/11/24 8:49 PM, Julian Waters
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAP2b4GO+NrzmS_hO5TNCwZ3XBRqXH4+AQkk=GQyhT7n3ty6U9g@mail.gmail.com">
<div dir="ltr">Ah, I see. Although, since the Port is going to be
deprecated if no one steps up to maintain it anyway, the bitrot
resulting from moving the Template Interpreter code into a
different directory might not matter too much. Sounds to me like
it might be less work than swapping to use a different
Interpreter altogether. Keeping the Template Interpreter until
the Port is removed might also help prevent 32 bit Linux Java
from suddenly degrading in performance, in my opinion
<div><br>
</div>
<div>best regards,</div>
<div>Julian</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jul 12, 2024 at
12:04 AM <<a href="mailto:coleen.phillimore@oracle.com" moz-do-not-send="true" class="moz-txt-link-freetext">coleen.phillimore@oracle.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 7/11/24 9:56 AM, Julian Waters wrote:<br>
> Wouldn't the removal of 32 bit Linux soon follow after
deprecation? <br>
> There wouldn't really be time to swap to using the Zero
Interpreter on <br>
> x86 if that happened<br>
><br>
We generally wait a release between deprecation and
obsolescence <br>
(removal), which would give time to switch to Zero.<br>
<br>
Coleen<br>
<br>
> best regards,<br>
> Julian<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>