Bug 180272
| Summary: | WebAssembly: don't set / reset the cached stack limit when not needed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | JF Bastien <jfbastien> |
| Component: | WebAssembly | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | fpizlo, jfbastien, keith_miller, mark.lam, msaboff, rmorisset, saam |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 179106 | ||
| Bug Blocks: | |||
JF Bastien
We currently have a cached stack limit on Instance, and we make sure to carefully set it to UINTPTR_MAX in places to avoid forgetting to reset it, in case an API user migrated the thread we run on. That has a runtime cost after every import call and after every indirect call, and it would be nice to not pay that cost if we know that there's no API caller who could migrate us.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |