-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
More Altivec Intrinsics #43492
More Altivec Intrinsics #43492
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
The failure seems again unrelated to my changeset... |
Hmm, it does, but it's not something we've seen before, and it seems plausible that your change could have caused it. Not sure what to do. |
The segfaults here look related to this PR (albeit roundaboutly) because it's only segfaulting on a specific powerpc test. My guess is that the modifications of |
Probably ade5ead whitelists features that aren't present in that version of llvm. |
Looks like CI may still have errors? |
My fix works only with llvm-4, llvm-3.7 has the feature available as non-NULL-terminated C arrays. I can add the hack of hardcoding the list sizes for the 3.7 and the 4.0 API to avoid a feature regression or just ifdef the 4.0 code and always return 0 otherwise. |
The function should accept feature strings that old LLVM might not support. Simplify the code using the same approach used by LLVMRustPrintTargetFeatures. Dummify the function for non 4.0 LLVM and update the tests accordingly.
@bors: r+ |
📌 Commit c471020 has been approved by |
⌛ Testing commit c471020 with merge 676d225bf643d08a120c64f5c3d36958678da3b6... |
☀️ Test successful - status-appveyor, status-travis |
👀 Test was successful, but fast-forwarding failed: 422 Update is not a fast forward |
☀️ Test successful - status-appveyor, status-travis |
Commit c471020 in rust-lang#43492 make `LLVMRustHasFeature` "more robust" by using `getFeatureTable()`. However, this function is specific to Rust's own LLVM fork, not upstream LLVM-4.0, so we need to use `#if LLVM_RUSTLLVM` to guard this call.
Taking Considering that this issue is about Altivec, it seems bad for the changeset to have a side effect on |
No description provided.