-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Properly check target_features
not to trigger an assertion
#89937
Conversation
This comment has been minimized.
This comment has been minimized.
The |
Hmm, I'm not sure about the right condition then. Since #89641, the target_features check has been moved to By the way, the test passes fine on my local and godbolt if I pass the target feature as a compile flag, but CI doesn't, any ideas? |
OK, so I spent a while looking through the changes in this PR and #89641. The original assert is still correct and shouldn't be removed. Instead the issue is in the
CI uses LLVM 10 and the error message seems to come from LLVM. LLVM 10 doesn't support the |
codegen_inline_asm
target_features
not to trigger an assertion
Thanks for the help! I think |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
`is_clobber()` already checks if `reg` is a register and the both values should be the same.
It now passes the tests, @Amanieu could you re-review? |
@bors r+ |
📌 Commit 12647ea has been approved by |
Properly check `target_features` not to trigger an assertion Fixes rust-lang#89875 I think it should be a condition instead of an assertion to check if it's a register as it's possible that `reg` is a register class. Also, this isn't related to the issue directly, but `is_target_supported` doesn't check `target_features` attributes. Is there any way to check it on rustc_codegen_llvm? r? `@Amanieu`
⌛ Testing commit 12647ea with merge cf1e3d5e2c954b4dc3401f78cbb87d285f642b03... |
💥 Test timed out |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a9b2bfb): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Fixes #89875
I think it should be a condition instead of an assertion to check if it's a register as it's possible that
reg
is a register class.Also, this isn't related to the issue directly, but
is_target_supported
doesn't checktarget_features
attributes. Is there any way to check it on rustc_codegen_llvm?r? @Amanieu