Skip to content

Rollup of 6 pull requests - #132020

Merged
bors merged 15 commits into
rust-lang:masterfrom
workingjubilee:rollup-a8iehqg
Oct 22, 2024
Merged

Rollup of 6 pull requests#132020
bors merged 15 commits into
rust-lang:masterfrom
workingjubilee:rollup-a8iehqg

Conversation

@workingjubilee

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

ShE3pyand others added 15 commits October 14, 2024 20:24
Update the list of reviewers after updating the team.
Co-authored-by: Jubilee <workingjubilee@gmail.com>
this saves about 150ms on many ./x invocations
…jubilee,pnkfelix
rust_for_linux: -Zregparm=<N> commandline flag for X86 (rust-lang#116972)
Command line flag `-Zregparm=<N>` for X86 (32-bit) for rust-for-linux: rust-lang#116972
Implemented in the similar way as fastcall/vectorcall support (args are marked InReg if fit).
`rt::Argument`: elide lifetimes
`@rustbot` label +C-cleanup
…ngjubilee
Always specify `llvm_abiname` for RISC-V targets
For RISC-V targets, when `llvm_abiname` is not specified LLVM will infer the ABI from the target features, causing rust-lang#116344 to occur. This PR adds the correct `llvm_abiname` to all RISC-V targets where it is missing (which are all soft-float targets), and adds a test to prevent future RISC-V targets from accidentally omitting `llvm_abiname`. The only affect of this PR is that `-Ctarget-feature=+f` (or similar) will no longer affect the ABI on the modified targets.
<!-- homu-ignore:start -->
r? `@RalfJung`
<!--- homu-ignore:end -->
…Kobzol
shave 150ms off bootstrap
This starts `git` commands inside `GitInfo`and the submodule updates in parallel. Git should already perform internal locking in cases where it needs to serialize a modification.
```
OLD
Benchmark #1: ./x check core
Time (mean ± σ): 608.7 ms ± 4.4 ms [User: 368.3 ms, System: 455.1 ms]
Range (min … max): 602.3 ms … 618.8 ms 10 runs
NEW
Benchmark #1: ./x check core
Time (mean ± σ): 462.8 ms ± 2.6 ms [User: 350.2 ms, System: 485.1 ms]
Range (min … max): 457.5 ms … 465.6 ms 10 runs
```
This should help with the rust-analyzer setup which issues many individual `./x check` calls. There's more that could be done but these were the lowest-hanging fruits that I saw.
…ests, r=fee1-dead
Move const trait tests from `ui/rfcs/rfc-2632-const-trait-impl` to `ui/traits/const-traits`
I found the old test directory to be somewhat long to name, and I don't think it's necessary to put an experimental implementation's tests under an rfc which is closed.
r? fee1-dead
Breaking this out of rust-lang#131985 so that PR doesn't touch 300 files.
…=scottmcm
Update triagebot.toml
Update the list of reviewers after updating the team here: rust-lang/team#1555
@rustbotrustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-testsuite Area: The testsuite used to check the correctness of rustc 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. rollup A PR which is a rollup labels Oct 22, 2024
@workingjubilee

Copy link
Copy Markdown
MemberAuthor

@bors r+ rollup=never p=6

@bors

bors commented Oct 22, 2024

Copy link
Copy Markdown
Collaborator

📌 Commit 0e307bb has been approved by workingjubilee

It is now in the queue for this repository.

@borsbors 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 Oct 22, 2024
@workingjubileeworkingjubilee added O-riscv Target: RISC-V architecture A-ABI Area: Concerning the application binary interface (ABI) O-x86_32 Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686) labels Oct 22, 2024
@bors

bors commented Oct 22, 2024

Copy link
Copy Markdown
Collaborator

⌛ Testing commit 0e307bb with merge f225713...

@bors

bors commented Oct 22, 2024

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: workingjubilee
Pushing f225713 to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Oct 22, 2024
@bors
bors merged commit f225713 into rust-lang:masterOct 22, 2024
@rustbotrustbot added this to the 1.84.0 milestone Oct 22, 2024
@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR#MessagePerf Build Sha
#130432rust_for_linux: -Zregparm= commandline flag for X86 (#11f705d43568e948c39d532a5e1ccdaf89b897e83c (link)
#131697rt::Argument: elide lifetimes44aff9aadefc400b4e7702968ba15395472ccf1d (link)
#131807Always specify llvm_abiname for RISC-V targetsc344a1cfa1178c79a2c28b56c5990b32f4dbbd10 (link)
#131954shave 150ms off bootstrap30c9b3d894fac4c6100a892feed544af0d01ddc9 (link)
#132015Move const trait tests from `ui/rfcs/rfc-2632-const-trait-i…e5f3bd8ac1eef67d29072a2905fa3d9b0f139acc (link)
#132017Update triagebot.toml4dcfcb6258f25e960a3efdc1369567a79d489191 (link)

previous master: 1de57a5ce9

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

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (f225713): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
0.4%[0.4%, 0.5%]2
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
--0
All ❌✅ (primary)--0

Max RSS (memory usage)

Results (primary 1.0%, secondary 0.8%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

meanrangecount
Regressions ❌
(primary)
2.4%[1.1%, 3.7%]2
Regressions ❌
(secondary)
0.8%[0.5%, 1.8%]4
Improvements ✅
(primary)
-1.7%[-1.7%, -1.7%]1
Improvements ✅
(secondary)
--0
All ❌✅ (primary)1.0%[-1.7%, 3.7%]3

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: 779.742s -> 781.092s (0.17%)
Artifact size: 333.70 MiB -> 333.68 MiB (-0.00%)

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ABIArea: Concerning the application binary interface (ABI)A-metaArea: Issues & PRs about the rust-lang/rust repository itselfA-testsuiteArea: The testsuite used to check the correctness of rustcmerged-by-borsThis PR was explicitly merged by bors.O-riscvTarget: RISC-V architectureO-x86_32Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)rollupA PR which is a rollupS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-libsRelevant 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.

10 participants

@workingjubilee@bors@rust-timer@rustbot@ShE3py@beetrees@azhogin@celinval@the8472@compiler-errors