Bump to 1.83

[BoxyUwU]

https://forge.rust-lang.org/release/process.html#bump-the-stable-version-number-t-6-days-friday-the-week-before

[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

[BoxyUwU]

@bors r+ rollup=never p=1

[bors]

📌 Commit 4d272b1 has been approved by BoxyUwU

It is now in the queue for this repository.

[bors]

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

[bors]

⌛ Testing commit 4d272b1 with merge 43eaa5c...

[bors]

☀️ Test successful - checks-actions
Approved by: BoxyUwU
Pushing 43eaa5c to master...

[rust-timer]

Finished benchmarking commit (43eaa5c): comparison URL.

Overall result: ❌✅ regressions and improvements - 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)	2.0%	[0.8%, 3.1%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.6%	[-1.9%, -0.3%]	12
All ❌✅ (primary)	2.0%	[0.8%, 3.1%]	2

Max RSS (memory usage)

Results (primary 0.4%, secondary 0.5%)

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.8%	[0.4%, 4.7%]	51
Regressions ❌ (secondary)	0.9%	[0.4%, 2.7%]	62
Improvements ✅ (primary)	-0.8%	[-1.9%, -0.4%]	15
Improvements ✅ (secondary)	-0.8%	[-2.0%, -0.4%]	20
All ❌✅ (primary)	0.4%	[-1.9%, 4.7%]	66

Cycles

Results (primary 0.4%, 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)	1.1%	[0.4%, 4.1%]	21
Regressions ❌ (secondary)	1.0%	[0.4%, 3.0%]	43
Improvements ✅ (primary)	-1.1%	[-4.6%, -0.5%]	9
Improvements ✅ (secondary)	-1.3%	[-5.3%, -0.4%]	54
All ❌✅ (primary)	0.4%	[-4.6%, 4.1%]	30

Binary size

Results (primary 0.7%)

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.7%	[0.7%, 0.7%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.7%	[0.7%, 0.7%]	1

Bootstrap: 789.249s -> 789.934s (0.09%)
Artifact size: 338.76 MiB -> 338.74 MiB (-0.01%)

[klensy]

Weird, but after that pr i can't build rust on x86_64-pc-windows-msvc, it fails with errors like:

librustc_llvm-6cacf3c42dd6ef43.rlib(LLParser.cpp.obj) : error LNK2001: unresolved external symbol __std_mismatch_8
librustc_llvm-6cacf3c42dd6ef43.rlib(EHStreamer.cpp.obj) : error LNK2001: unresolved external symbol __std_mismatch_4
librustc_llvm-6cacf3c42dd6ef43.rlib(LoopUnroll.cpp.obj) : error LNK2001: unresolved external symbol __std_replace_8

(Locally bumped msvc to 17.11.4, probably it's the reason?)

mehh, auto update of msvc don't consistently updated toolchain, manual update fixed issue.

[jieyouxu]

Hi @klensy, I think someone else is running into this, could you elaborate what you updated? (This seems more like a msvc toolchain issue not a rust issue)

[klensy]

Hi @klensy, I think someone else is running into this, could you elaborate what you updated? (This seems more like a msvc toolchain issue not a rust issue)

Yes, after automatic update, need to go into modify -> individual components -> found installed build tools (was build tools 14.40-17.10), uncheck old one (to uninstall it) and select newer one (build tools 14.41-17.11), then install it.

[jieyouxu]

Yes, after automatic update, need to go into modify -> individual components -> found installed build tools (was build tools 14.40-17.10), uncheck old one (to uninstall it) and select newer one (build tools 14.41-17.11), then install it.

Thanks for the info, this is slightly funny lol.