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

[chenggwang]

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.It's not a high priority, and it's not really a bug

[chenggwang]

@Palmr I don't think it's going to cause a barrier loss. Do you think that's okay?

[chenggwang]

Can anyone help review this?Thanks！

[Palmr]

There's already a version of this in the code for benchmarking, see SequenceVarHandle.java

As noted in SequenceBenchmark.java we felt the manual barriers were nicer since they cut down on boxing and casting.

As you say, "It's not a high priority, and it's not really a bug" so it's unlikely this PR will be merged unless some befit can be found and demonstrated.

[chenggwang]

There's already a version of this in the code for benchmarking, see SequenceVarHandle.java

As noted in SequenceBenchmark.java we felt the manual barriers were nicer since they cut down on boxing and casting.

As you say, "It's not a high priority, and it's not really a bug" so it's unlikely this PR will be merged unless some befit can be found and demonstrated.

OK