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

Avoid resolving method_kind in AbstractInterpreter::can_be_compiled

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 10
    • Fix Version/s: 10
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b21

      Description

      compilationPolicy.cpp calls AbstractInterpreter::can_be_compiled during linking and resolve steps, which is somewhat costly and affects startup:

        if (!AbstractInterpreter::can_be_compiled(m)) {
          return false;
        }

      It would seem that rather than resolving the method_kind(m) in can_be_compiled, it would suffice to switch on m->intrinsic_id():

      switch (m->intrinsic_id()) {
            case vmIntrinsics::_dsin : // fall thru
          ...

      This significantly reduces the cost of AbstractInterpreter::can_be_compiled

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              redestad Claes Redestad
              Reporter:
              redestad Claes Redestad
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: