-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Rollup of 9 pull requests #145978
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
Rollup of 9 pull requests #145978
Conversation
The submodule->subtree changes add a lot of commits with the GitHub email.
This commit adds an empty stub for the function for QNX 8 targets. This symbol is required by the unwinder but is not present, causing a linking failure when building with the standard library. Address review feedback: use whitelist for QNX versions
Add a mailmap entry for gnzlbg The submodule->subtree changes add a lot of commits with the GitHub email.
…tgross35 implement Sum and Product for Saturating(u*) ACP: rust-lang/libs-team#604 `@rustbot` label +needs-fcp
…l, r=tgross35 fix(std): Fix undefined reference to __my_thread_exit on QNX 8.0 When cross-compiling for the x86_64/aarch64-unknown-nto-qnx800 target (QNX SDP 8.0), the build fails during the final link stage with the error: ``` error: linking with `qcc` failed: exit status: 1 ... = note: undefined reference to `__my_thread_exit' ``` - **On QNX 7.1**: The __my_thread_exit symbol is defined and exported by the main C library (libc.a/libc.so). The std backtrace code can therefore successfully take its address at compile time. - **On QNX 8.0**: As part of a toolchain modernization, this symbol has been refactored. It is no longer present in any of the standard system libraries (.a or .so). This patch addresses the problem at its source by conditionally compiling the problematic code. Fixes rust-lang#142726
Remove TmpLayout in layout_of_enum 09a3846 from <rust-lang#103693> made LayoutData be owned instead of interned in `Variants::Multiple::variants`[^1], so there's no need for `TmpLayout` in layout_of_enum anymore, and we can just store the variants' layouts directly in the prospective `LayoutData`s' `variants` fields. This should have no effect on semantics or layout. (written as part of rust-lang#145337 but not related to the layout optimizations in that PR) [^1]: see line 1154 of `compiler/rustc_target/src/abi/mod.rs` in the linked commit; `Variants::Multiple::variants` effectively changed from `IndexVec<.., Layout<'tcx>>` to `IndexVec<.., LayoutData>` where the `LayoutData`s are not interned as `Layout`s (`LayoutData` was at the time called `LayoutS`)
…k-Simulacrum std library: use execinfo library also on NetBSD. The execinfo library is also available on NetBSD.
…lacrum Test `instrument-mcount` codegen Closes rust-lang#92109 by testing that a call to `mcount` is actually emitted
…=Kobzol Add more to the `[workspace.dependencies]` section in the top-level `Cargo.toml` Following on from rust-lang#145740. r? `@Kobzol`
fix `core::marker::Destruct` doc `~const` bounds are now `[const]` I think... Related: rust-lang#143874, rust-lang#133214
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: ef8d1d6f5b In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing ef8d1d6 (parent) -> 41f2b6b (this PR) Test differencesShow 14 test diffsStage 1
Stage 2
Additionally, 8 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 41f2b6b39e7526a28d50ff6918dda6de48add5e4 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
…ieyouxu tests: Ignore basic-stepping.rs on riscv64 Same as [PR 145745](rust-lang#145745) r? `@lqd`
Finished benchmarking commit (41f2b6b): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 3.2%, secondary -1.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 465.841s -> 466.755s (0.20%) |
Successful merges:
instrument-mcount
codegen #145884 (Testinstrument-mcount
codegen)[workspace.dependencies]
section in the top-levelCargo.toml
#145947 (Add more to the[workspace.dependencies]
section in the top-levelCargo.toml
)core::marker::Destruct
doc #145972 (fixcore::marker::Destruct
doc)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup