-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Added support for apxf
target feature
#139534
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
Added support for apxf
target feature
#139534
Conversation
r? @SparrowLii rustbot has assigned @SparrowLii. Use |
970fb61
to
336c5f9
Compare
336c5f9
to
282deb3
Compare
This comment has been minimized.
This comment has been minimized.
282deb3
to
d7bc563
Compare
This comment has been minimized.
This comment has been minimized.
d7bc563
to
b3e9d21
Compare
This comment has been minimized.
This comment has been minimized.
b3e9d21
to
c0626b5
Compare
This comment has been minimized.
This comment has been minimized.
c0626b5
to
994c752
Compare
This comment has been minimized.
This comment has been minimized.
994c752
to
eaf714b
Compare
This comment has been minimized.
This comment has been minimized.
eaf714b
to
6c4b6dc
Compare
I would be grateful if a perf-run could be initiated for this PR. I think I do not have sufficient privileges for initiating it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, do run ./x check tidy
before you push, it ensures that CI won't fail right away due to tidy checks
Sry I'm not familar with llvm so |
6c4b6dc
to
99b5a86
Compare
Have updated |
b260411
to
9d85006
Compare
Just to clarify, |
iiuc, the reason |
9d85006
to
3ac1f53
Compare
cool, this looks reasonable, have to doublecheck if I need to check about target features with someone first before approving this, I think |
Got it 😊 |
☔ The latest upstream changes (presumably #140633) made this pull request unmergeable. Please resolve the merge conflicts. |
Ah found the documentation again, and I do not need to consult anyone for this feature. Yay. Rebase? and I'll get it this time. |
3ac1f53
to
f59bcee
Compare
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
Just rebased this branch and I noticed a bunch of changes to |
Cargo.lock shouldn't have been modified, might just be a mistake from git. You probably have to revert it |
There should not need to be any Cargo.lock changes as part of this PR. |
f59bcee
to
c32dc2d
Compare
Thank you! Should be good to go. @bors r+ rollup |
Rollup of 9 pull requests Successful merges: - rust-lang#134273 (de-stabilize bench attribute) - rust-lang#139534 (Added support for `apxf` target feature) - rust-lang#140419 (Move `in_external_macro` to `SyntaxContext`) - rust-lang#140483 (Comment on `Rc` abort-guard strategy without naming unrelated fn) - rust-lang#140607 (support duplicate entries in the opaque_type_storage) - rust-lang#140656 (collect all Fuchsia bindings into the `fuchsia` module) - rust-lang#140668 (Implement `VecDeque::truncate_front()`) - rust-lang#140709 (rustdoc: remove unportable markdown lint and old parser) - rust-lang#140713 (Structurally resolve in `check_ref_cast` in new solver) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#139534 - madhav-madhusoodanan:apx-target-feature-addition, r=workingjubilee Added support for `apxf` target feature
Thank you so much @sayantn @workingjubilee for helping me in this PR 🙏 Learnt quite a bit about adding targets to rustc |
Context
apxf
target feature, which is dependent upon the LLVM featuresegpr
,push2pop2
,ppx
,ndd
,ccmp
,nf
,cf
andzu
.LLVMFeature
from anOption
to aSmallVec
to support multiple dependencies.Associated Issue
cc: @sayantn