bump few deps

[klensy]

Bumps cargo_metadata, thorin-dwp, windows.

Should dedupe some crates around.

[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]

Some changes occurred in src/tools/compiletest

cc @jieyouxu

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[jieyouxu]

Bumps LGTM, I'll let Mark double-check though. I'm surprised if nothing breaks especially for windows crate bumps from 0.52.0 -> 0.57.0.

[klensy]

Well, compiler builds locally on my win machine; hopefully no stike back from memchr.

[rustbot]

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

[bors]

☔ The latest upstream changes (presumably #129624) made this pull request unmergeable. Please resolve the merge conflicts.

[jieyouxu]

Actually since this doesn't touch libs deps, this seems fine.

[jieyouxu]

Thanks!
@bors r+ rollup=iffy (bump deps)

[bors]

📌 Commit 62d92e6 has been approved by jieyouxu

It is now in the queue for this repository.

[bors]

⌛ Testing commit 62d92e6 with merge 739668d...

[bors]

💔 Test failed - checks-actions

[tgross35]

@bors retry

CI can't reach docker right now #130946 (comment)

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[bors]

⌛ Testing commit 62d92e6 with merge 851f698...

[bors]

☀️ Test successful - checks-actions
Approved by: jieyouxu
Pushing 851f698 to master...

[rust-timer]

Finished benchmarking commit (851f698): 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)	3.4%	[3.4%, 3.4%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	3.4%	[3.4%, 3.4%]	1

Max RSS (memory usage)

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

Cycles

Results (primary 4.1%, secondary -2.2%)

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)	4.1%	[3.3%, 4.9%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.2%	[-2.2%, -2.2%]	1
All ❌✅ (primary)	4.1%	[3.3%, 4.9%]	2

Binary size

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

Bootstrap: 774.209s -> 771.075s (-0.40%)
Artifact size: 341.42 MiB -> 341.37 MiB (-0.02%)

[Kobzol]

Noise:

[Kobzol]

@rustbot label: +perf-regression-triaged

[klensy]

In windows 0.53 (https://github.com/microsoft/windows-rs/releases/tag/0.53.0) was added microsoft/windows-rs#2786 and now rustc_driver links to propsys.dll, but i can't find why it's linked and where actually used yet.

microsoft/windows-rs#3282 changes something around, but not released yet, maybe fixed this?

Checked, issue fixed in unreleased version of windows crate.