From aph-open at littlepinkcloud.com Wed Sep 7 09:59:00 2022 From: aph-open at littlepinkcloud.com (Andrew Haley) Date: Wed, 7 Sep 2022 10:59:00 +0100 Subject: [aarch64-port-dev ] Fwd: Does OpenJDK have plans to provide Windows Arm64EC port? Message-ID: <6407d942-b3bc-c509-86a4-8b6bd7d6dff8@littlepinkcloud.com> -------- Forwarded Message -------- From: Glavo Date: Wed, 7 Sep 2022 15:29:41 +0800 Message-ID: Subject: Does OpenJDK have plans to provide Windows Arm64EC port? To: aarch64-port-dev at openjdk.org Many native libraries do not yet support Windows on Arm, but the performance of executing Java applications through x86 emulation is very poor. If OpenJDK provides an Arm64EC port, the above problem would be solved, so I wonder if anyone is working on this. From martijnverburg at gmail.com Wed Sep 7 10:10:26 2022 From: martijnverburg at gmail.com (Martijn Verburg) Date: Wed, 7 Sep 2022 11:10:26 +0100 Subject: [aarch64-port-dev ] Fwd: Does OpenJDK have plans to provide Windows Arm64EC port? In-Reply-To: <6407d942-b3bc-c509-86a4-8b6bd7d6dff8@littlepinkcloud.com> References: <6407d942-b3bc-c509-86a4-8b6bd7d6dff8@littlepinkcloud.com> Message-ID: Hi all, >From a Microsoft perspective, this is not currently on our roadmap (and is not expected to be scheduled ). We (Developer Division as a whole) will focus on improving the native developer toolchain (Visual Studio, WSL) so that lib authors can build natively for the platform. Cheers, Martijn On Wed, 7 Sept 2022 at 11:00, Andrew Haley wrote: > -------- Forwarded Message -------- > From: Glavo > Date: Wed, 7 Sep 2022 15:29:41 +0800 > Message-ID: 4dNsy8OnHR_zi5U_yHumLzfiuwDMHmr-VF0_FaC7Bg at mail.gmail.com> > Subject: Does OpenJDK have plans to provide Windows Arm64EC port? > To: aarch64-port-dev at openjdk.org > > Many native libraries do not yet support Windows on Arm, but the > performance of executing Java applications through x86 emulation is very > poor. > If OpenJDK provides an Arm64EC port, the above problem would be solved, so > I wonder if anyone is working on this. > -------------- next part -------------- An HTML attachment was scrubbed... URL: