Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

#456 Directly replace Fence with the methods setRelease, setVolatile, and getAcquire. No need to set barriers via VarHandle #457

Closed
wants to merge 2 commits into from
Closed

#456 Directly replace Fence with the methods setRelease, setVolatile, and getAcquire. No need to set barriers via VarHandle #457

wants to merge 2 commits into from

Commits on Sep 15, 2023

  1. directly replace Fence with the methods setRelease, setVolatile, and … 

    …getAcquire

Since we already have VALUE_FIELD, it is more semantically clear to directly replace Fence with the methods setRelease, setVolatile, and getAcquire. No need to set barriers via VarHandle
    @chenggwang
    chenggwang authored Sep 15, 2023
    Configuration menu
    Copy the full SHA
    15542cd View commit details
    Browse the repository at this point in the history

  2. directly replace Fence with the methods setRelease, setVolatile, and … 

    …getAcquire

Since we already have VALUE_FIELD, it is more semantically clear to directly replace Fence with the methods setRelease, setVolatile, and getAcquire. No need to set barriers via VarHandle
    @chenggwang
    chenggwang authored Sep 15, 2023
    Configuration menu
    Copy the full SHA
    72522f8 View commit details
    Browse the repository at this point in the history