vm.defmeth tests should be structured to avoid unresolved classes

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: hotspot
    • None

      While investigating 8152903, I was curious why this only showed up with AOT. The problem is that the classes are unresolved at the point where regular JITs try to compile it. C1 will handle this but both C2 and Graal will emit an uncommon trap for the very first thing in the test method. Some simple restructuring of the test would make it a more effective compiler test.

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

              Created:
              Updated:
              Resolved: