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

max_heap_for_compressed_oops() declared with size_t, but defined with uintx

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P5
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
      gc
    • Resolved In Build:
      b17

      Backports

        Description

        From http://mail.openjdk.java.net/pipermail/hotspot-dev/2014-May/014020.html

        I've created a patch [1] to fix usage of uintx where size_t type is
        expected in hotspot/src/share/vm/runtime/arguments.cpp

        The Arguments::max_heap_for_compressed_oops() method is declared in
        arguments.hpp as
        size_t max_heap_for_compressed_oops()
        but later defined in arguments.cpp as
        uintx max_heap_for_compressed_oops()

        For most platforms the uintx and size_t types are effectively the
        same, so the interchange is uncaught, but on s390 (32-bit) the size_t is
        "unsigned long" which makes it incompatible with "unsigned int".

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tschatzl Thomas Schatzl
                  Reporter:
                  tschatzl Thomas Schatzl
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: