Lambda: Invokespecial gets an IncompatibleClassChangeError when it should get AbstractMethodError

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • hs25
    • Affects Version/s: hs25
    • Component/s: hotspot
    • b55
    • generic
    • generic

        With the addition of interfacemethodref to invokespecial and invokestatic, and the updated JVMS 0.63 draft spec, invokespecial and invokestatic need to not throw IncompatibleClassChangeError if they use an interfacemethodref that resolves to an abstract method. Invokevirtual needs to throw an IncompatibleClassChangeError if it gets an interfacemethodref.

              Assignee:
              Karen Kinnear (Inactive)
              Reporter:
              Karen Kinnear (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: