Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tooling: JS+wasm dead code stripping #434

Merged
merged 2 commits into from
Oct 30, 2015
Merged

Tooling: JS+wasm dead code stripping #434

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f23a77f
Tooling: JS+wasm dead code stripping
jfbastien Oct 29, 2015
da78aee
Update wording to follow surrounding code
jfbastien Oct 29, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Tooling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,12 @@ The tooling we expect to support includes:
- Instrumentation-based.
* Process dump: local variables, call stack, heap, global variables, list of
threads.
* JavaScript+WebAssembly size optimization tool. Some developers have huge
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but all the other bullet points are a name + :. Perhaps change the first . to :? In which case, maybe also edit to remove the later : to avoid repetition.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I updated the sentence, and shortened it so it fits better with the surrounding.

applications which today cross-compile to JavaScript and call to hand-written
JavaScript code. With WebAssembly they would ship as WebAssembly+JavaScript
mixed applications: lots of WebAssembly, calling to JavaScript libraries which
communicate with the rest of the Web platform. Tooling is needed to perform
dead code stripping and global optimization across the API boundary.

In many cases, the tooling will be pure WebAssembly without any tool-specific
support from WebAssembly. This won't be possible for debugging, but should be
Expand Down