Split passes into different categories

Open
#2 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, wasm
Domain
tooling

Research direction

Review the repository's existing Binaryen pass handling, then compare it with the linked initial experiments and example project. Determine whether the proposed speed, size, and debugging categories are complete and well-defined. Done means the categories and pass assignments have an agreed scope and are implemented consistently.

Written by the indexing model from the issue text.

Description

discussion good first issue help wanted

Currently, there are 57 passes that are available in Binaryen. With this pile of passes, it's difficult to decide what passes should be used for some general yet specific task (e.g reduce the size or speed up the execution). There is an idea to split it into multiple categories for each passes. Some categories that I can think of are:

  • optimization related to speed up the execution
  • optimization related to reducing the binary size
  • passes which produce something that can help the debug process

I have done some initial work by trying some passes if it shrinks the size using this example. Still not sure if it's correct.

Dominant language
JavaScript
Stars
3
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 DrSensor/binaryen-loader

All issues in DrSensor/binaryen-loader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.