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

zero-based Compressed Oops are used instead of 32-bits Oops on windows-amd64

    • generic
    • generic

      The following heap parameters cause "zero based Compressed Oops" to be used, while "zero based Compressed Oops, 32-bits Oops" are expected:

      1.
      .../windows-amd64//bin/java -server -Xmixed -XX:+UseSerialGC -XX:ObjectAlignmentInBytes=8 -XX:HeapBaseMinAddress=1600m -Xmx800m -XX:MaxPermSize=800m -XX:+UnlockDiagnosticVMOptions -XX:+PrintCompressedOopsMode -version

      heap address: 0x000000079c000000, size: 1600 MB, zero based Compressed Oops

      2.
      .../windows-amd64//bin/java -server -Xmixed -XX:+UseSerialGC -XX:ObjectAlignmentInBytes=8 -XX:HeapBaseMinAddress=1500m -Xmx850m -XX:MaxPermSize=850m -XX:+UnlockDiagnosticVMOptions -XX:+PrintCompressedOopsMode -version

      heap address: 0x0000000795c00000, size: 1700 MB, zero based Compressed Oops

      3.
      .../windows-amd64//bin/java -server -Xmixed -XX:+UseSerialGC -XX:ObjectAlignmentInBytes=8 -XX:HeapBaseMinAddress=1536m -Xmx2048m -XX:MaxPermSize=512m -XX:+UnlockDiagnosticVMOptions -XX:+PrintCompressedOopsMode -version

      heap address: 0x0000000760000000, size: 2560 MB, zero based Compressed Oops

      All instances 1-3 are specific to windows-amd64.

            Unassigned Unassigned
            sdolgovorcl Sergey Dolgov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: