llvm: Update reliable_f128 configuration for LLVM22 on Sparc#154119
Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom Mar 21, 2026
Merged
llvm: Update reliable_f128 configuration for LLVM22 on Sparc#154119rust-bors[bot] merged 1 commit intorust-lang:mainfrom
reliable_f128 configuration for LLVM22 on Sparc#154119rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
LLVM22 should have resolved issues with the `f128` ABI, meaning we can now set `cfg(target_has_reliable_f128)` on the platform. Link: llvm/llvm-project@3e16aef
rustbot
added
A-LLVM
Contributor
Author
|
Hang on, checking something on godbolt |
rustbot
removed
the
S-waiting-on-review
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
rustbot
added
the
S-waiting-on-author
Contributor
Author
|
Nevermind, everything looks all good, I just don't know my sparc targets. https://rust.godbolt.org/z/o1ExW4fMY @rustbot ready Cc maintainers of sparc targets @psumbera @kulikjak @jonathanpallant: if you get the chance, it would be good to run the testsuite for |
rustbot
added
S-waiting-on-review
Contributor
Author
|
Forgot this exists now, @bors try jobs=dist-sparcv9-solaris |
This comment has been minimized.
This comment has been minimized.
rust-bors bot
pushed a commit
that referenced
this pull request
Mar 19, 2026
llvm: Update `reliable_f128` configuration for LLVM22 on Sparc try-job: dist-sparcv9-solaris
Contributor
Member
|
Looks good - let's go ahead and merge, then the cced maintainers can use an actual nightly build to confirm later. @bors r+ rollup |
Contributor
rust-bors
bot
added
S-waiting-on-bors
rust-bors bot
pushed a commit
that referenced
this pull request
Mar 20, 2026
…uwer Rollup of 5 pull requests Successful merges: - #153828 (Guard patterns: lowering to THIR) - #154015 (refactor - moving `check_stability` check to `parse_stability`) - #154119 (llvm: Update `reliable_f128` configuration for LLVM22 on Sparc) - #154138 (vec::Drain::fill: avoid reference to uninitialized memory) - #154143 (test copy_specializes_from_vecdeque: reduce iteration count for Miri)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LLVM22 should have resolved issues with the
f128ABI, meaning we can now setcfg(target_has_reliable_f128)on the platform.Link: llvm/llvm-project@3e16aef
Since we're on the topic,
r? @cuviper