RFC: 32-bit x86 port maintenance, stepping down as maintainer

[coleen.phillimore at oracle.com]

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.

Coleen

On 7/11/24 8:49 PM, Julian Waters wrote:
> 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
>
> best regards,
> Julian
>
> On Fri, Jul 12, 2024 at 12:04 AM <coleen.phillimore at oracle.com> wrote:
>
>
>
>     On 7/11/24 9:56 AM, Julian Waters wrote:
>     > Wouldn't the removal of 32 bit Linux soon follow after deprecation?
>     > There wouldn't really be time to swap to using the Zero
>     Interpreter on
>     > x86 if that happened
>     >
>     We generally wait a release between deprecation and obsolescence
>     (removal), which would give time to switch to Zero.
>
>     Coleen
>
>     > best regards,
>     > Julian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20240712/7678a488/attachment.htm>