github-actions[bot] commented on Issue #2077:
Subscribe to Label Action
cc @bnjbvr, @peterhuene
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:area:aarch64", "cranelift:area:machinst", "cranelift:meta", "cranelift:wasm", "wasmtime:api"Thus the following users have been cc'd because of the following labels:
- bnjbvr: cranelift
- peterhuene: wasmtime:api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
julian-seward1 commented on Issue #2077:
On further reflection, I am inclined to rename two of the new AArch64
instructions so as to be more consistent with CLIF. At the CLIF level, the
patch adds 5 new instructions:atomic_rmw, atomic_cas, atomic_load, atomic_store, fence
At the AArch64 level, the corresponding new instructions are
LLSC, CAS, AtomicLoad, AtomicStore, Fence.
I am thinking these should actually be
AtomicRMW, AtomicCAS, AtomicLoad, AtomicStore, Fence.
Implying, via the name, that the first of these (
LLSC
) contains an LL-SC loop
is misleading, since any atomic modification of memory will require use of LL
and SC.CAS
also uses LL and SC, for example. Also, it would be better not
to imply the use of LL and SC at all, since some AArch64 revisions after 8.0
support compare-and-swap directly (I think), and so we could emit those
differently on such targets in future.Reviewers: any objections to the proposed renaming?
cfallin commented on Issue #2077:
+1 to the proposed
Inst
names. In particularAtomicLLSC
->AtomicRMW
; the latter corresponds to the actual semantics, the former is an implementation detail.
cfallin edited a comment on Issue #2077:
+1 to the proposed
Inst
names. In particularLLSC
->AtomicRMW
; the latter corresponds to the actual semantics, the former is an implementation detail.
Last updated: Nov 22 2024 at 17:03 UTC