Rollup of 5 pull requests

[Centril]

Successful merges:

• Avoid more symbol interning #61035 (Avoid more symbol interning)
• PGO - Add a smoketest for combining PGO with cross-language LTO. #61036 (PGO - Add a smoketest for combining PGO with cross-language LTO.)
• Don't arena-allocate static symbols. #61077 (Don't arena-allocate static symbols.)
• Ship profiler with windows-gnu #61080 (Ship profiler with windows-gnu)
• Fix spelling in release notes #61149 (Fix spelling in release notes)

Failed merges:

r? @ghost

[Centril]

@bors r+ p=5 rollup=never

[bors]

📌 Commit 5c60c50 has been approved by Centril

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout rollup-rh5cd2y (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self rollup-rh5cd2y --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

warning: Cannot merge binary files: Cargo.lock (HEAD vs. heads/homu-tmp)
Auto-merging src/libsyntax_ext/asm.rs
Auto-merging src/libsyntax/parse/parser.rs
Auto-merging src/libsyntax/ext/tt/macro_rules.rs
Auto-merging src/libsyntax/ext/tt/macro_parser.rs
Auto-merging src/libsyntax/ext/base.rs
Auto-merging Cargo.lock
CONFLICT (content): Merge conflict in Cargo.lock
Automatic merge failed; fix conflicts and then commit the result.

[Centril]

OK... this makes no sense; I tested all 3 rollups in a single PR and there were no conflicts.