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

Cleanup NativePostCallNop

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 23
    • 21, 22, 23
    • hotspot
    • b05

      Cleanup NativePostCallNop

      NativePostCallNop and uses of it should be refactored for better separation of shared code from platform details.

      - Shared code (e.g. `install_post_call_nop_displacement()`) assumes that a NativePostCallNop can encode 4 bytes of data: 1 byte for the oomap slot and 3 bytes for the offset of the NativePostCallNop in the CodeBlob. It should be left to the platforms how the data is encoded and how many bits are used for oopmap slot / cb offset.

      - There is no difference in the implementations of `frame::get_oop_map()`. It should be moved to shared code.

            rrich Richard Reingruber
            rrich Richard Reingruber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: