RESOLVED FIXED 276504
[WASM] Compute B3 effect ranges for memory and global ops in OMG 
https://bugs.webkit.org/show_bug.cgi?id=276504
Summary [WASM] Compute B3 effect ranges for memory and global ops in OMG
David Degazio
Reported 2024-07-11 13:39:52 PDT
Currently OMG does not explicitly specify effect ranges for any of the B3 memory values it generates, meaning they all implicitly take on the maximal HeapRange::top(). But we know statically that different WASM instructions will touch strictly disjoint regions of memory - i32.store may write any address in the current WASM memory, but it can never overwrite a global. And global 0 can't overlap with global 1 or 2. Let's compute B3 HeapRanges for these disjoint effect regions to enable B3 to better deduplicate and hoist loads and stores generated by OMG.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-07-11 13:40:03 PDT
<rdar://problem/131562611>
David Degazio
Comment 2 2024-07-17 15:00:57 PDT
Pull request: https://github.com/WebKit/WebKit/pull/30924
EWS
Comment 3 2024-07-19 11:54:13 PDT
Committed 281143@main (958d1de8af7b): <https://commits.webkit.org/281143@main> Reviewed commits have been landed. Closing PR #30924 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.