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
I ran into this bug on #8719 but the current definition of i64_from_iconst can match the f32const and f64const nodes in addition to iconst. This seems counterintuitive given the name of the extractor, but I'm not sure how to best fix myself.
The text was updated successfully, but these errors were encountered:
Previously this extractor would additionally match `f32const` and
`f64const` which while theoretically not the end of the world can be
confusing. Nowadays switch it to instead only matching the `iconst`
instruction, as the name implies, and if necessary matching float
constants is probably best done through separate ISLE lowering rules.
Closesbytecodealliance#8723
Previously this extractor would additionally match `f32const` and
`f64const` which while theoretically not the end of the world can be
confusing. Nowadays switch it to instead only matching the `iconst`
instruction, as the name implies, and if necessary matching float
constants is probably best done through separate ISLE lowering rules.
Closes#8723
I ran into this bug on #8719 but the current definition of
i64_from_iconst
can match thef32const
andf64const
nodes in addition toiconst
. This seems counterintuitive given the name of the extractor, but I'm not sure how to best fix myself.The text was updated successfully, but these errors were encountered: