-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Support removed LLVM intrinsics by invoking its AutoUpgrade mechanism. #35261
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=1 Giving higher priority since it'd be nice to see this in nightly. |
📌 Commit 63f0c4d has been approved by |
⌛ Testing commit 63f0c4d with merge 0a3180b... |
Support removed LLVM intrinsics by invoking its AutoUpgrade mechanism. Turns out that LLVM sometimes renames platform intrinsics or replaces them with first-class instructions. For example, signed minimum became `select (icmp SLT, a, b), a, b` where `a` and `b` are vectors. This is blocking the Servo rustup ([relevant failure](http://build.servo.org/builders/windows-dev/builds/226/steps/compile/logs/stdio)), as they're using a few such intrinsics. The fix in this PR is to invoke LLVM's own `AutoUpgrade` mechanism to do the replacements.
Do we want a tracking issue/TODO for when we drop support for the last LLVM which still supports the call natively? |
💔 Test failed - auto-linux-64-debug-opt |
@bors retry |
@bors force |
Turns out that LLVM sometimes renames platform intrinsics or replaces them with first-class instructions.
For example, signed minimum became
select (icmp SLT, a, b), a, b
wherea
andb
are vectors.This is blocking the Servo rustup (relevant failure), as they're using a few such intrinsics.
The fix in this PR is to invoke LLVM's own
AutoUpgrade
mechanism to do the replacements.