[vello_cpu]: add WASM vello_cpu examples #1076
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LaurenzV
approved these changes
Jul 2, 2025
|
Yeah - |
taj-p
approved these changes
Jul 2, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
ajakubowicz-canva
force-pushed
the
ajakubowicz-vello_cpu-example
branch
from
6f407ce to
5309be3
Compare
LaurenzV
pushed a commit
that referenced
this pull request
Jul 2, 2025
### Context To help with performance profiling and inspecting vello_cpu example renders on the browser, this PR adds a vello_cpu examples. Run with `cargo run_wasm -p wasm_cpu --release` ### Scenes added We don't yet have a rendering abstraction between `vello_cpu` and `vello_hybrid`, so the example scenes are pretty similar, but not quite identical. I simplified each one to use `RenderContext` instead of `Scene`, and also made them very specific to running on the browser. I added: - simple - tiger svg - cowboy image - text - clipping No new assets are added in this PR - only existing assets in the repo are used. See the screen recording to see the scenes added. ### Test plan > [!Note] > Passing the +simd128 rustc flags spams the console with `(ignoring feature)` logs. This is because the run-wasm tool is built for your system architecture with the same global flags – and because it's not wasm it doesn't recognize the feature. Everything still works. Test it by running it with `cargo run_wasm -p wasm_cpu --release` and test explicit SIMD by running `RUSTFLAGS=-Ctarget-feature=+simd128 cargo run_wasm -p wasm_cpu --release`. ### Screen recording https://github.com/user-attachments/assets/80867362-bce5-4a9e-b303-88b2c9233972 (cherry picked from commit e7a75ec)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
To help with performance profiling and inspecting vello_cpu example renders on the browser, this PR adds a vello_cpu examples.
Run with
cargo run_wasm -p wasm_cpu --releaseScenes added
We don't yet have a rendering abstraction between
vello_cpuandvello_hybrid, so the example scenes are pretty similar, but not quite identical. I simplified each one to useRenderContextinstead ofScene, and also made them very specific to running on the browser.I added:
No new assets are added in this PR - only existing assets in the repo are used. See the screen recording to see the scenes added.
Test plan
Note
Passing the +simd128 rustc flags spams the console with
(ignoring feature)logs. This is because the run-wasm tool is built for your system architecture with the same global flags – and because it's not wasm it doesn't recognize the feature. Everything still works.Test it by running it with
cargo run_wasm -p wasm_cpu --releaseand test explicit SIMD by runningRUSTFLAGS=-Ctarget-feature=+simd128 cargo run_wasm -p wasm_cpu --release.Screen recording
output.mp4