Skip to content

[dart2wasm] Revisit binaryen flags we use when compiling apps #60931

Open
@mkustermann

Description

@mkustermann

The list of binaryen flags we have been using hasn't been changed in a long time, despite us having added various optimizations on our side, including more devirtualization of calls (including closure calls), ...

We also have now a good set of large applications that compile under dart2wasm we can use as a measurement stick:

  • Wonderous
  • DevTools
  • Flute
  • ACX Gallery
  • Hello world

We should re-visit the binaryen passes we run (order, number and type of pass) while not only looking at the size of the above, but also aiming for spending less compilation-time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-dart2wasmIssues for the dart2wasm compiler.type-performanceIssue relates to performance or code size

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions