Skip to content

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Sep 13, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

camsteffen and others added 30 commits September 5, 2025 20:22
The Rust Embedded Devices Working Group (wg-embedded) Arm Team (t-arm)
agreed to listed as maintainers of:

* aarch64-unknown-none
* aarch64-unknown-none-softfloat
* armv7a-none-eabi
* armv7r-none-eabi
* armv7r-none-eabihf

The aarch64-unknown-none* target didn't have a page so I added it.

wg-embedded t-arm did not want to take over:

* armebv7r-none-eabi
* armebv7r-none-eabihf

So I gave them their own target page. The current maintainer remains.
This reverts commit 7ce620d.
The const-hacks introduces bugs, and they make the code harder to maintain.
Let's wait until we can constify these functions without changing their implementation.
Removes a bunch of information that isn't, strictly speaking, target specific.
This is important to note, as it affects how easy it is to build a
binary, and that `#![no_std]` is mandatory.

A different PR should probably add this to all the other platform pages.
and document `VaList::arg`.
as far as I can see this was not tested, though the error message was already implemented
…unctions

they don't do anything, because LLVM is unable to inline c-variadic functions (on most targets, anyway)
…wuable, r=workingjubilee

Document `become` keyword

The feature is not yet implemented, so I'm not sure if we should merge this _right away_, promoting an incomplete feature is probably not the best idea. But the docs can be reviewed while the implementation work is being done.
…enkov

Some hygiene doc improvements

Improve some doc comments around SyntaxContext, outer_expn and friends.

Based on discussion at rust-lang#146100.

r? petrochenkov
…leLapkin

tidy: check that error messages don't start with a capitalized letter
…r=workingjubilee

Update the arm-* and aarch64-* platform docs.

This PR updates some of the arm*-unknown-none target docs, and adds some missing target pages.

## aarch64-none-elf and aarch64-none-elf-softfloat

The Rust Embedded Devices Working Group's Arm Team is added as a maintainer, and a target page is added. Links are added to the EDWG's support crates for this target.

## armv7a-none-eabi and armv7a-none-eabihf

The Rust Embedded Devices Working Group's Arm Team is added as a maintainer, and a target page is added. Links are added to the EDWG's support crates for this target.

## armv7r-none-eabi and armv7r-none-eabihf

The Rust Embedded Devices Working Group's Arm Team is added as a maintainer, and the target page is split from the Big Endian versions. Links are added to the EDWG's support crates for this target.

## armebv7r-none-eabi and armveb7r-none-eabihf

The target page is split from the Little Endian versions. No change in maintainers.

I have agreement to add EDWG/T-Arm as maintainers, which was voted upon in [their repo](rust-embedded/wg#851).
…rkingjubilee

Revert "Constify SystemTime methods"

This reverts rust-lang#144519. The const-hacks introduces bugs, and they make the code harder to maintain. Let's wait until we can constify these functions without changing their implementation.

Fixes rust-lang#146228.
Closes rust-lang#144517 (since the feature is gone).
r? `@tgross35`
Cc `@clarfonthey`
…=workingjubilee

document `core::ffi::VaArgSafe`

tracking issue: rust-lang#44930

A modification of rust-lang#146454, keeping just the documentation changes, but not unsealing the trait.

Although conceptually we'd want to unseal the trait, there are many edge cases to supporting arbitrary types. We'd need to exhaustively test that all targets/calling conventions support all types that rust might generate (or generate proper error messages for unsupported cases). At present, many of the `va_arg` implementations assume that the argument is a scalar, and has an alignment of at most 8. That is totally  sufficient for an MVP (accepting all of the "standard" C types), but clearly does not cover all rust types.

This PR also adds some various other tests for edge cases of c-variadic:

- the `#[inline]` attribute in its various forms. At present, LLVM is unable to inline c-variadic functions, but the attribute should still be accepted. `#[rustc_force_inline]` already rejects c-variadic functions.
- naked functions should accept and work with a C variable argument list. In the future we'd like to allow more ABIs with naked functions (basically, any ABI for which we accept defining foreign c-variadic functions), but for now only  `"C"` and `"C-unwind` are supported
- guaranteed tail calls: c-variadic functions cannot be tail-called. That was already rejected, but there was not test for it.

r? `@workingjubilee`
@rustbot rustbot added A-tidy Area: The tidy tool F-explicit_tail_calls `#![feature(explicit_tail_calls)]` O-hermit Operating System: Hermit O-SGX Target: SGX O-solid Operating System: SOLID O-unix Operating system: Unix-like O-wasi Operating system: Wasi, Webassembly System Interface O-windows Operating system: Windows S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Sep 13, 2025
@jhpratt
Copy link
Member Author

jhpratt commented Sep 13, 2025

@bors r+ rollup=never p=5

@rustbot rustbot added the rollup A PR which is a rollup label Sep 13, 2025
@bors
Copy link
Collaborator

bors commented Sep 13, 2025

📌 Commit da1c27d has been approved by jhpratt

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 13, 2025
@bors
Copy link
Collaborator

bors commented Sep 13, 2025

⌛ Testing commit da1c27d with merge a015919...

@bors
Copy link
Collaborator

bors commented Sep 14, 2025

☀️ Test successful - checks-actions
Approved by: jhpratt
Pushing a015919 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Sep 14, 2025
@bors bors merged commit a015919 into rust-lang:master Sep 14, 2025
11 checks passed
@rustbot rustbot added this to the 1.91.0 milestone Sep 14, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#113095 Document become keyword a2a0944105945699e1f0a1c3e181480ffc0c1936 (link)
#146159 Some hygiene doc improvements 821c32ad73cd00df41dd96833cf1e08d6c922fae (link)
#146171 tidy: check that error messages don't start with a capitali… 30030667657ee7074297e51183f5bbe3f57d76f6 (link)
#146419 Update the arm-* and aarch64-* platform docs. 366e678cb795f630c9c94eb92db80447ec7f1857 (link)
#146473 Revert "Constify SystemTime methods" 27b4fbc13203ac18cf87349c97a1eaa665927d47 (link)
#146506 Fix small typo in check-cfg.md 0190edb2e3886a097234236af89eb564022dd85e (link)
#146517 fix Condvar::wait_timeout docs 0c7da054e11c9cffbef512238beb7a99d7f756ab (link)
#146521 document core::ffi::VaArgSafe 65c953d403cb0aaa31cd45952e4684f5748d03fe (link)

previous master: 02c7b1a7ac

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

Copy link
Contributor

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 02c7b1a (parent) -> a015919 (this PR)

Test differences

Show 286 test diffs

Stage 1

  • [codegen] tests/codegen-llvm/cffi/c-variadic-inline.rs: [missing] -> pass (J2)
  • [ui] tests/ui/c-variadic/naked.rs: [missing] -> pass (J2)
  • [ui] tests/ui/explicit-tail-calls/c-variadic.rs: [missing] -> pass (J2)

Stage 2

  • [ui] tests/ui/c-variadic/naked.rs: [missing] -> ignore (only executed when the operating system is linux) (J0)
  • [ui] tests/ui/c-variadic/naked.rs: [missing] -> pass (J1)
  • [ui] tests/ui/c-variadic/naked.rs: [missing] -> ignore (only executed when the architecture is x86_64) (J3)
  • [ui] tests/ui/explicit-tail-calls/c-variadic.rs: [missing] -> pass (J4)
  • [codegen] tests/codegen-llvm/cffi/c-variadic-inline.rs: [missing] -> pass (J5)

Additionally, 278 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard a015919e54c60b1b2bec7a98dec478cfc4a48f4e --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-x86_64-apple: 7217.3s -> 9657.9s (33.8%)
  2. x86_64-gnu-llvm-19: 2426.6s -> 2839.0s (17.0%)
  3. pr-check-1: 1364.2s -> 1574.8s (15.4%)
  4. i686-gnu-2: 5475.4s -> 6115.4s (11.7%)
  5. aarch64-gnu-llvm-19-1: 3238.1s -> 3606.4s (11.4%)
  6. aarch64-gnu-debug: 3786.9s -> 4207.2s (11.1%)
  7. i686-gnu-nopt-1: 7326.3s -> 8114.8s (10.8%)
  8. dist-s390x-linux: 4858.6s -> 5363.1s (10.4%)
  9. dist-aarch64-msvc: 6248.4s -> 5615.0s (-10.1%)
  10. x86_64-rust-for-linux: 2646.0s -> 2914.2s (10.1%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (a015919): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.1% [0.1%, 0.1%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (secondary -2.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.2% [-2.2%, -2.2%] 1
All ❌✅ (primary) - - 0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 473.393s -> 475.072s (0.35%)
Artifact size: 390.19 MiB -> 390.15 MiB (-0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tidy Area: The tidy tool F-explicit_tail_calls `#![feature(explicit_tail_calls)]` merged-by-bors This PR was explicitly merged by bors. O-hermit Operating System: Hermit O-SGX Target: SGX O-solid Operating System: SOLID O-unix Operating system: Unix-like O-wasi Operating system: Wasi, Webassembly System Interface O-windows Operating system: Windows rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.