Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISLE i64_from_iconst extractor can match f32const/f64const #8723

Closed
alexcrichton opened this issue May 31, 2024 · 0 comments · Fixed by #8739
Closed

ISLE i64_from_iconst extractor can match f32const/f64const #8723

alexcrichton opened this issue May 31, 2024 · 0 comments · Fixed by #8739

Comments

@alexcrichton
Copy link
Member

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.

alexcrichton added a commit to alexcrichton/wasmtime that referenced this issue Jun 3, 2024
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 bytecodealliance#8723
github-merge-queue bot pushed a commit that referenced this issue Jun 4, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant