Bump version to 1.64.0

[pietroalbini]

r? @ghost

[pietroalbini]

@bors r+ rollup=never p=9

[bors]

📌 Commit 5f015a2 has been approved by pietroalbini

[bors]

⌛ Testing commit 5f015a2 with merge f3a416f97613e5572cefe3c67a9412480c338569...

[bors]

💥 Test timed out

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

[Mark-Simulacrum]

@bors retry hang on crates io index checkout?

[bors]

⌛ Testing commit 5f015a2 with merge e02d645...

[bors]

☀️ Test successful - checks-actions
Approved by: pietroalbini
Pushing e02d645 to master...

[rust-timer]

Finished benchmarking commit (e02d645): comparison url.

Instruction count

• Primary benchmarks: 😿 relevant regressions found
• Secondary benchmarks: 😿 relevant regressions found

	mean1	max	count2
Regressions 😿 (primary)	0.3%	0.4%	2
Regressions 😿 (secondary)	0.7%	0.8%	6
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-0.4%	-0.4%	1
All 😿🎉 (primary)	0.3%	0.4%	2

Max RSS (memory usage)

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

Cycles

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

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

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

Footnotes

1. the arithmetic mean of the percent change ↩

2. number of relevant changes ↩

[rylev]

Looks like there is some new noise in the keccak benchmark. Marking this as triaged.

@rustbot label: +perf-regression-triaged