Use MemoryAddress instead of MemorySegment in CLinker::upcallStub

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • None
    • Affects Version/s: repo-panama
    • Component/s: tools

      CLinker::upcallStub used to return a MemorySegment, mostly to allow deterministic closing. Now that deterministic closing is handled in the ResourceScope passed to upcallStub, we can just return a MemoryAddress, which is more correct from an API perspective (as the segment returned by upcallStub is not really for dereference).

            Assignee:
            Maurizio Cimadamore
            Reporter:
            Maurizio Cimadamore
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: