Bug 282168
| Summary: | Fix exceptions in WasmOMGIRGenerator32_64 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Angelos Oikonomopoulos <angelos> |
| Component: | JavaScriptCore | Assignee: | Angelos Oikonomopoulos <angelos> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | simontaylor1, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Angelos Oikonomopoulos
Need to properly initialize the EncodedJSValue.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Angelos Oikonomopoulos
Pull request: https://github.com/WebKit/WebKit/pull/35790
EWS
Committed 285766@main (bca4ade201f5): <https://commits.webkit.org/285766@main>
Reviewed commits have been landed. Closing PR #35790 and removing active labels.
Radar WebKit Bug Importer
<rdar://problem/138774127>
Simon Taylor
Would this be responsible for the issue with -fwasm-exception that affected our codebase in iOS 18.0?
I reported more details here on the emscripten github: https://github.com/emscripten-core/emscripten/issues/24600
Emscripten are willing to explore adding a workaround if it's possible to avoid triggering this bug, but will likely need some more input from the webkit team about the specific triggers and whether a workaround would be possible.
Thanks
Angelos Oikonomopoulos
This issue and fix are only relevant for 32-bit platforms and this code has never been on by default on them in any case. So unfortunately the answer to your question would be "no".