[JVMCI] be more precise when enforcing OopMapValue encoding limitations

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 9
    • Component/s: hotspot
    • b127

      HotSpotVMConfig.maxFrameSize is currently used to enforce the stack offset encoding limitations of OopMapValue by limiting frame size, but the value isn't quite right since it doesn't take into account the space stolen for registers. Instead we should enforce the encoding limitation directly and provide an appropriate constant that clients can use detect or handle this problem.

            Assignee:
            Tom Rodriguez
            Reporter:
            Tom Rodriguez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: