C2: Manage non-debug safepoint edges in structural manner

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: 26
    • Component/s: hotspot

      There are multiple places where non-debug inputs are added to safepoints, but there's no functionality to separate different types of edges, so it's easy to break things when different flavors mix. (In particular, reachability edges introduced by JDK-8290892, derived oops, exception oops during parsing, valid_length_test_input on array allocation runtime calls).

      Track non-debug inputs of different types separately and let corresponding code query the type of non-debug inputs it is interested in.

            Assignee:
            Unassigned
            Reporter:
            Vladimir Ivanov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: