-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Register allocation failure on x86_64 with simd enabled #3160
Comments
A reduction of this appears to be:
|
|
The |
The issue appears to be that the lowering for
with an Separately, I think that the discussion that led to "we don't generate this CLIF from any Wasm so we don't need to support the case with zero or one extends" is somehow wrong -- we're clearly getting it here. @jlb6740 I think we may need to just implement the general case? |
(For clarity, the "unsupported case" is supposed to hit the panic a bit further down, rather than silently not generate instructions) |
@jlb6740 there was another fuzzbug that came in today related to this -- would you mind taking a look when you're able? |
@cfallin Sorry guys. I do not notice alerts when I'm tagged so missed this but I did see 3161 and submitted a fix for that .. which fixes this too. |
@alexcrichton I can no longer reproduce this after #3209. I will close, but please reopen as necessary. |
Found via fuzz-bugs last night using this test case yields:
I'll try to reduce this in a bit
The text was updated successfully, but these errors were encountered: