On Tue, 13 Aug 2024 09:35:41 GMT, Aleksey Shipilev wrote:
> As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
> are about to deprecate the port for removal. It makes little sense to
> continue testing the port, and thus block development and integration of new
> feat
On Tue, 13 Aug 2024 09:35:41 GMT, Aleksey Shipilev wrote:
> As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
> are about to deprecate the port for removal. It makes little sense to
> continue testing the port, and thus block development and integration of new
> feat
On Tue, 13 Aug 2024 09:35:41 GMT, Aleksey Shipilev wrote:
> As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
> are about to deprecate the port for removal. It makes little sense to
> continue testing the port, and thus block development and integration of new
> feat
On Tue, 13 Aug 2024 09:35:41 GMT, Aleksey Shipilev wrote:
> As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
> are about to deprecate the port for removal. It makes little sense to
> continue testing the port, and thus block development and integration of new
> feat
On Tue, 13 Aug 2024 09:35:41 GMT, Aleksey Shipilev wrote:
> As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
> are about to deprecate the port for removal. It makes little sense to
> continue testing the port, and thus block development and integration of new
> feat
As planned in [JDK-8338285](https://bugs.openjdk.org/browse/JDK-8338285), we
are about to deprecate the port for removal. It makes little sense to continue
testing the port, and thus block development and integration of new features.
Ahead of that JEP, we can separately decide to disable the x86
