You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I attempt to optimize it with optimizeLevel > 1. The problem goes away if I remove the second
(drop
(call$ref_is_null
(local.get$0)
)
)
from the function or make $0 a function parameter, so I guess that there is an optimization trying to move/copy local values around that causes this as soon as there are two local.gets of the same anyref local or something along those lines. This isn't overly important, just ran into this while trying to polyfill ref.null etc. so we can have shiny things. Perhaps there's an easy fix?
The text was updated successfully, but these errors were encountered:
This adds support for the reference type proposal. This includes support
for all reference types (`anyref`, `funcref`(=`anyfunc`), and `nullref`)
and four new instructions: `ref.null`, `ref.is_null`, `ref.func`, and
new typed `select`. This also adds subtype relationship support between
reference types.
This does not include table instructions yet. This also does not include
wasm2js support.
Fixes#2444 and fixes#2447.
I'm currently trying to track down a Binaryen assertion happening with the following module:
which yields
when I attempt to optimize it with optimizeLevel > 1. The problem goes away if I remove the second
from the function or make
$0
a function parameter, so I guess that there is an optimization trying to move/copy local values around that causes this as soon as there are twolocal.get
s of the same anyref local or something along those lines. This isn't overly important, just ran into this while trying to polyfillref.null
etc. so we can have shiny things. Perhaps there's an easy fix?The text was updated successfully, but these errors were encountered: