Rollup of 6 pull requests - #161041
Open
JonathanBrouwer wants to merge 24 commits into
Open
Conversation
The 20 word requirement was likely from the JS EH ABI which we no longer support.
This matches other targets.
And change the dummy impl to use __rust_abort to match panic_abort.
the new `sym::complex` in the previous commit pushes some symbol from 999 to 1000, which causes the formatting change here
LLVM23 includes the ABI fix to make f128 work [1]. That version isn't yet stable, but at least the type will start getting picked up in top-of-tree CI. While addressing this, also update the comment regarding f16. [1]: llvm/llvm-project@aa47e59
…kertdev x86_64-win: Enable f128 on LLVM 23+ LLVM23 includes the ABI fix to make f128 work [1]. That version isn't yet stable, but at least the type will start getting picked up in top-of-tree CI. While addressing this, also update the comment regarding f16. [1]: llvm/llvm-project@aa47e59
…laumeGomez rustdoc: use anonymous constant for primitives/keywords/attribute docs For context: [#t-rustdoc > hiding fake_item modules. @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/hiding.20fake_item.20modules.2E/near/612115954) r? @GuillaumeGomez I've rendered the standard library docs and prims/kws/attrs all show up as normal. However I could not figure out how to run some of the tests, so this may be a bit of CI-debugging for me :(
…mulacrum Couple of misc improvements to the unwind infrastructure * Fix `_Unwind_Exception` size on Emscripten. * Move a link block. * Remove some manual dummy impls where there is already a dummy fallback. Follow up to rust-lang#159785
…e, r=Amanieu PowerPC inline ASM: Fix scalar floats being in the wrong vector lane on little endian 64-bit PowerPC supports both big and little endian, however registers are always big endian. As a consequence of this, the order of vector lanes is reversed on little endian; however scalar `f32` and `f64` are always stored in the actual (big-endian) lane 0. This PR fixes the LLVM ASM fixup to take that into account. Ping target maintainers: @daltenty @gilamn5tr @amy-kwan @Gelbpunkt @famfo @neuschaefer
…ngjubilee Add `core::num::Complex` tracking issue: rust-lang#154023 See also [#t-compiler > representing &rust-lang#96;_Complex&rust-lang#96;](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/representing.20.60_Complex.60/with/608308993). The RFC states that the `Complex` type should match the ABI of `_Complex` in C, but provides little detail on how to actually achieve this. We concluded that `repr(complex)` is probably the best approach. Like clang, that means we "desugar" the representation early: `_Complex` is not natively represented in LLVM IR. I've derived the ABI from `clang` for 28 targets, a decent sample of what we actually support. For now I'm only actually testing `x86_64` because (as you'll see) updating the tests is quite labor-intensive. If we're happy with this direction I can fill more of them in, likely in a separate PR. The libs side of the type is very bare-bones: I'm not as interested in that part. Others can fill in the various instances, methods, write tests for those, and improve the docs. r? workingjubilee
…lock-label-suggestion, r=folkertdev Fix invalid suggestion from try unlabled block Fixes rust-lang#160987 I wondering whether `unsafe` and `const` with block have similar issue, and found we don't give out code suggestion for these scenarios, maybe could be improved in another PR.
rustbot
added
A-attributes
rustbot
added
S-waiting-on-review
Contributor
Author
Contributor
rust-bors
Bot
added
S-waiting-on-bors
Contributor
|
⌛ Trying commit 851e090 with merge c39b604… To cancel the try build, run the command Workflow: https://github.com/rust-lang/rust/actions/runs/31691164887 |
rust-bors Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
Rollup of 6 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2
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
8 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.
Successful merges:
core::num::Complex#158885 (Addcore::num::Complex)r? @ghost
Create a similar rollup