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

IncompatibleClassChangeError expected for 2 or more maximally-specific matching methods

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: hs25
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b59

      Backports

        Description

        Given the following (indirectly compiled in such a way to avoid errors):

        interface K { int m() default { return 99; } }
        interface L { int m() default { return 101; } }
        interface J extends K, L {}
        interface I extends J, K { int m() default { J.super.m(); } }
        class C implements I {}

        C c = new C(); c.m(); // expected: ICCE; actual no error

        An IncompatibleClassChangeError is expected but none is thrown. c.m() links to K.m().

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                acorn Karen Kinnear (Inactive)
                Reporter:
                psandoz Paul Sandoz
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Due:
                  Created:
                  Updated:
                  Resolved: