Bump stdarch

[daxpedda]

This bumps stdarch to rust-lang/stdarch@684de0d to get in rust-lang/stdarch#1677 (tracked in #133908).

From the commit history I deduced that there shouldn't be any changes to Rust necessary.

From past PRs I'm assuming that bumping stdarch like this is fine, but please let me know if this is somehow inappropriate or requires something more to be done!

try-job: arm-android
try-job: armhf-gnu

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

⚠️ Warning ⚠️

• These commits modify submodules.

[daxpedda]

Fixed failure in rust-lang/stdarch#1692.

[daxpedda]

r? @Amanieu

I think is more appropriate.

[Amanieu]

@bors r+

[bors]

📌 Commit f90a536 has been approved by Amanieu

It is now in the queue for this repository.

[daxpedda]

@Amanieu I think something went wrong here and it didn't end up in the queue.

[Amanieu]

@bors ping

[bors]

😪 I'm awake I'm awake

[Amanieu]

@bors r+ rollup

[bors]

💡 This pull request was already approved, no need to approve it again.

[bors]

📌 Commit f90a536 has been approved by Amanieu

It is now in the queue for this repository.

[Amanieu]

@bors rollup=never

[bors]

⌛ Testing commit f90a536 with merge 17e6acb...

[Amanieu]

@bors rollup=maybe

[Amanieu]

@bors delegate+

[bors]

✌️ @daxpedda, you can now approve this pull request!

If @Amanieu told you to "r=me" after making some further change, please make that change, then do @bors r=@Amanieu

[daxpedda]

try-jobs are still not triggered. I will continue to try it out with r+ unfortunately.

@bors r+

[bors]

📌 Commit 923aba9 has been approved by daxpedda

It is now in the queue for this repository.

[daxpedda]

@bors r+

[bors]

📌 Commit db651a0 has been approved by daxpedda

It is now in the queue for this repository.

@bors r+

📌 Commit 374800b has been approved by daxpedda

It is now in the queue for this repository.

While we are at it:
@bors rollup=never

⌛ Testing commit 374800b with merge 409998c...

☀️ Test successful - checks-actions
Approved by: daxpedda
Pushing 409998c to master...

Finished benchmarking commit (409998c): comparison URL.

Overall result: ✅ improvements - 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.

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

Max RSS (memory usage)

Results (primary 2.9%, secondary 0.3%)

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)	5.4%	[2.5%, 10.7%]	6
Regressions ❌ (secondary)	4.1%	[4.1%, 4.1%]	1
Improvements ✅ (primary)	-4.3%	[-5.9%, -2.7%]	2
Improvements ✅ (secondary)	-3.4%	[-3.4%, -3.4%]	1
All ❌✅ (primary)	2.9%	[-5.9%, 10.7%]	8

Cycles

Results (secondary 3.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.

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

Binary size

Results (primary -0.0%)

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)	0.1%	[0.0%, 0.3%]	6
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.1%	[-0.6%, -0.0%]	22
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-0.0%	[-0.6%, 0.3%]	28

Bootstrap: 762.9s -> 763.56s (0.09%)
Artifact size: 330.67 MiB -> 330.63 MiB (-0.01%)