Portable SIMD subtree update

[calebzulawski]

Syncs nightly to the latest changes from rust-lang/portable-simd

r? @rust-lang/libs

[bors]

⌛ Testing commit 4d96078 with merge 54b4148...

[bors]

💔 Test failed - checks-actions

[calebzulawski]

That's silly, I thought core::arch::x86_64 always existed when building docs. Anyway, I removed the link. @workingjubilee hope this works 🙃

[workingjubilee]

@bors r+

[bors]

📌 Commit bcb1c41 has been approved by workingjubilee

It is now in the queue for this repository.

[workingjubilee]

@calebzulawski Docs are primarily for the user, their ability to be hosted on docs.rs or other docs sites is secondary: that's a choice a user gets to make. Which means docs are built, primarily, for informing you about what's available for the specific build configuration you did. Every crate has to configure docs.rs metadata to get something hostable if there's no defaults.

[bors]

⌛ Testing commit bcb1c41 with merge 3f1e30a...

[bors]

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

[calebzulawski]

whew

[rust-timer]

Finished benchmarking commit (3f1e30a): comparison URL.

Overall result: ❌ regressions - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	0.7%	[0.3%, 2.1%]	14
Regressions ❌ (secondary)	1.3%	[0.2%, 2.2%]	23
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.7%	[0.3%, 2.1%]	14

Max RSS (memory usage)

Results

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.

	mean	range	count
Regressions ❌ (primary)	1.9%	[1.0%, 2.7%]	4
Regressions ❌ (secondary)	1.9%	[0.9%, 3.3%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	1.9%	[1.0%, 2.7%]	4

Cycles

Results

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.

	mean	range	count
Regressions ❌ (primary)	2.0%	[1.5%, 2.5%]	2
Regressions ❌ (secondary)	2.3%	[0.7%, 4.4%]	12
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	2.0%	[1.5%, 2.5%]	2

Binary size

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

Bootstrap: 670.8s -> 672.666s (0.28%)
Artifact size: 313.92 MiB -> 313.96 MiB (0.01%)

[lqd]

Strange regression, but mostly on doc builds. Could be std/core metadata changes.

[calebzulawski]

Yeah, idk. I wouldn't expect these changes to affect performance. Maybe there are more trait implementations? I can't think of anything significant

[workingjubilee]

yeah, if we add a function then there's more docs to generate, them's the breaks.

[rylev]

yeah, if we add a function then there's more docs to generate, them's the breaks.

Seems reasonable to me

@rustbot label: +perf-regression-triaged