[lworld] Revisit memory barrier requirements around inline type allocations

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P3
    • repo-valhalla
    • Affects Version/s: repo-valhalla
    • Component/s: hotspot

      InlineTypeBaseNode::buffer currently adds a StoreStore barrier to not let stores that initialize this buffer be reordered with a subsequent store that would make this buffer accessible by other threads.

      We should evaluate the impact of the barrier which is potentially blocking other optimizations and re-visit the fixes of the linked bugs.

      We should also re-visit the barrier code in Parse::array_load.

            Assignee:
            Unassigned
            Reporter:
            Tobias Hartmann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: