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

[lworld] Scalarize inline type receiver through default method calls


    • Type: Enhancement
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: repo-valhalla
    • Fix Version/s: repo-valhalla
    • Component/s: hotspot
    • Labels:


      From a discussion with [~jrose]:

      John Rose:
      The other case which I’m trying to get at is harder, because it requires specialization. Suppose there is a default method in the interface, whose receiver is of the interface type itself. That’s the problem I’m trying to push on here: Calling this method on an inline reciever appears to require buffering, to match up with the calling sequence of the default method. And there’s no way to guess at which inline types (implementors of that interface) might eventually execute that default method on themselves. The good case is if (a) the default method call is devirtualized and inlined; then you basically get a custom copy of the default method, just for that inline receiver and for that call site. The not-so-good case is if inlining fails (maybe the default method is a complex algorithm); that case seems to require that the method fall all the down to full polymorphism.
      I’d like to see a story where such a default method (and if we do abstract supers for inlines, then non-abstract methods in abstract supers) gets recompiled for each inline receiver that needs it. That way it doesn’t need to be inlined in order to operate at full speed.

      Tobias Hartmann:
      If the abstract interface method is implemented by an inline receiver method, and if the reciever is already scalarized in the caller, then I suppose the call is devirtualized, and the scalarized receiver in the caller is copied to the entry point of the callee method. Right?
      Correct. The virtual call will always be devirtualized in that case and the receiver will be passed in a scalarized form. If the callee is C2 compiled as well, no handshake is required. Otherwise, buffering in the entry point of the C1 compiled callee or the c2i adapter (for the interpreter) is necessary.
      For the default method scenario, which requires specialization of the method, we first need support for multiple compiled methods per Java method (JDK-8038356). We then need to make sure that the devirtualized call points to the specialized method which requires that the specialized method is available before the caller is (re-)compiled.


          Issue Links



              • Assignee:
                thartmann Tobias Hartmann
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: