Order of immediates on atomic GC accessors

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
wasm
Domain
compilers

Research direction

The issue names no files. Start by reading the linked acquire-release-atomics PR 29 to see the proposed immediate order, then find the current [ordering] typeidx immediate on the atomic GC struct and array accessors in this repo's spec text. Done means the team has agreed on a final immediate order, with the spec wording updated to match, and that decision is a design call for maintainers.

Written by the indexing model from the issue text.

Description

The intersection of the acquire-release-atomics proposal and multi-byte array access proposal gives this order of immediates for multi-byte array loads and stores: [flags] [memidx | typeidx] [ordering] [offset] (see https://github.com/WebAssembly/acquire-release-atomics/pull/29).

Currently, atomic GC accessors have this order of immediates: [ordering] typeidx.

We may want to change the order of immediates on GC accessors to be e.g. struct.atomic.get $t seqcst to better match the proposed order for loads and stores.

Dominant language
WebAssembly
Stars
101
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/shared-everything-threads

All issues in WebAssembly/shared-everything-threads

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.