[CLEAN] Synthetic Benchmark PR #48788 - fix: enable wasm trap handlers in all Node.js processes #19
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.
Benchmark PR electron#48788
Type: Clean (correct implementation)
Original PR Title: fix: enable wasm trap handlers in all Node.js processes
Original PR Description: #### Description of Change
Found while investigating microsoft/vscode#273191
Since electron#47186 we had accidentally disabled V8 trap handlers in browser and utility process. This incurs performance cost when executing wasm due to inlined bound checks.
Enable the feature back and align it with upstream based on the feature parameter across all processes features::kWebAssemblyTrapHandler
Current matrix of enabled platforms.
Release Notes
Notes: Reenable V8 trap handlers for wasm in browser and utility process, improves runtime execution of wasm
Original PR URL: electron#48788