Moving profiles and relaxed SIMD forward

Open
#175 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
compilers

Research direction

Start by reading the issue alongside the linked Relaxed SIMD and Profiles proposals, the Profiles issue #6, and meeting pull request #1377. Done means the project has resolved the relationship between the two proposals and reached a decision on the proposed votes and profile procedure.

Written by the indexing model from the issue text.

Description

After the recent CG meeting (TODO: link notes once uploaded), we need to pin down how we're advancing the intertwined Relaxed SIMD and Profiles proposals - we previously determined that Relaxed SIMD would have a dependency on the existence of a "deterministic" profile.

Here's my view on how votes for moving these forward should be structured:

  • We should vote on relaxed SIMD to phase 4 in the in-person meeting. This vote will imply editorial changes to the spec to create the syntactic framework for profiles and exactly two profiles ("full" and "deterministic") - the poll question can reflect this. No procedural mechanism will be established for adding any further profiles.

  • The profiles "proposal" should be interpreted as a consensus vote on establishing new procedure to evaluate and introduce future profiles - such as the suggested "no-gc" profile. Maybe this means that it shouldn't be called a proposal any more, but simply a vote on a procedural change - a more ambitious version of our previous phase advancement process changes. This debate+vote may take longer to work through (see https://github.com/WebAssembly/profiles/issues/6), and the relaxed SIMD vote above does not depend on it.

In the case that the first vote passes but the latter process never completes, this would result in "full" and "deterministic" indefinitely being the only profiles in the specification.

Dominant language
Python
Stars
1.1k
Forks
78
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/proposals

All issues in WebAssembly/proposals

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.