David Degazio

Move SpeculativeJIT::compileNewArray operand.use() calls to separate loop

1

#### 5d17a6f6dfb77a1fb2ed2e205069cf37f39459c3 Move SpeculativeJIT::compileNewArray operand.use() calls to separate loop https://bugs.webkit.org/show_bug.cgi?id=246307 rdar://100497797 Reviewed by NOBODY (OOPS!). * Source/JavaScriptCore/dfg/DFGSpeculativeJIT.cpp: https://github.com/WebKit/WebKit/commit/5d17a6f6dfb77a1fb2ed2e205069cf37f39459c3 | Misc | iOS, tvOS & watchOS | macOS | Linux |...

Should there be a special case in assert_return for ref.null in the JS spec harness?

1

On the wasm-3.0 branch, there's a few cases in the spec tests where an `assert_return` expects to get a `ref.null`, like in [this test from select.wast](https://github.com/WebAssembly/spec/blob/wasm-3.0%2Bannot/test/core/select.wast#L280C1-L280C66): ```wast (assert_return (invoke "join-funcnull"...

wasm-as/wasm-dis seem to miscompile ref.null with type-index heap type

8

I've noticed some seemingly incorrect behavior in binaryen working with one of the cases from the [`br_if.wast` spec test on the wasm-3.0 branch](https://github.com/WebAssembly/spec/blob/wasm-3.0/test/core/br_if.wast#L666-L679): ```wast (module (type $t (func)) (func $f...