Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8339784

Implement JEP 479: Remove the Windows 32-bit x86 Port

XMLWordPrintable

    • Icon: CSR CSR
    • Resolution: Approved
    • Icon: P3 P3
    • 24
    • hotspot
    • None
    • behavioral
    • high
    • The removal of the Windows 32-bit x86 port means that the latest OpenJDK changes will no longer be available for the 32-bit Windows platform.
    • Other
    • JDK

      Summary

      Remove the Windows 32-bit x86 port.

      Goals

      • Update the build system to issue an error message when an attempt is made to configure a build for Windows 32-bit x86 (x86-32).

      • Mark the port, and related port-specific features, as removed in the relevant documentation.

      Non-Goals

      • It is not a goal to change the status of the affected port in any prior release. The earliest release to which this JEP could be targeted is JDK 24.

      • It is not a goal to remove any other 32-bit port.

      Motivation

      • Allow contributors in the OpenJDK Community to accelerate the development of new features and enhancements that will move the platform forward.

      • The implementation of JEP 436 (Virtual Threads) for Windows x86-32 falls back to the use of kernel threads and therefore does not bring the expected benefits of Project Loom.

      • Windows 10, the last Windows operating system to support 32-bit operation, will reach End of Life in October 2025.

      Description

      An attempt to configure a Windows x86-32 build will produce the following output:

      $ bash ./configure --with-target-bits=32
      ...
      checking compilation type... native
      configure: error: 32-bit Windows builds are not supported
      configure exiting with result code 1
      $

      Risks and Assumptions

      32-bit JVMs are still used on Windows due to integration with 32-bit native libraries (DLLs). Their users cannot migrate directly to 64-bit JVMs because a 64-bit process on Windows cannot load 32-bit DLLs. While Windows x64 is capable of running 32-bit applications by emulating an 32-bit environment through WOW64, applications will suffer dramatic performance degradation despite the assumed memory footprint benefits.

      We therefore assume that

      • Users can continue to run existing builds of the Windows 32-bit JVM to integrate with native 32-bit libraries and, if necessary, expose 32-bit functionality via remote APIs to be consumed by applications running on a 64-bit JVM within the same environment; and

      • Legacy systems are unlikely to migrate to versions of the JDK following the release of Java 21.

            swesonga Saint Wesonga
            swesonga Saint Wesonga
            Joe Darcy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: