Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12525

Update RISC-V instructions for ACQUIRE/RELEASE barriers

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • Storage Engines
    • 5
    • 2024-05-28 - FOLLOW ON SPRINT

      We've recently renamed our READ/WRITE_BARRIER to ACQUIRE/RELEASE_BARRIERs in WT-12167 and WT-12170, but only made changes to the inline assembly for our supported architectures.

      RISC-V is not a supported architecture, but the changes to fence instructions look like a quick win since the fences look like
          fence <instructions before>, <instructions after>
      As an example the release barrier can become
          {{{}fence rw, w
      {}}}which aligns with the definition of release semantics.

      We should still review the RISC-V docs to check for any surprises, but strengthening these barriers is safe and aligns behaviour with our acquire/release macros

            Assignee:
            luke.pearson@mongodb.com Luke Pearson
            Reporter:
            andrew.morton@mongodb.com Andrew Morton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: