Rollup of 8 pull requests

[tgross35]

Successful merges:

• enable -Zrandomize-layout in debug CI builds  #101339 (enable -Zrandomize-layout in debug CI builds )
• Add target support for RTEMS Arm #127021 (Add target support for RTEMS Arm)
• bypass linker configuration and cross target check for specific commands #128871 (bypass linker configuration and cross target check for specific commands)
• [rustdoc] Sort impl associated items by kinds and then by appearance #129471 ([rustdoc] Sort impl associated items by kinds and then by appearance)
• Add test to build crates used by r-a on stable #129529 (Add test to build crates used by r-a on stable)
• Run cargo update in the project root #129624 (Adjust memchr pinning and run cargo update)
• Unify scraped examples with other code examples #129796 (Unify scraped examples with other code examples)
• explain why Rvalue::Len still exists #129939 (explain why Rvalue::Len still exists)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[rust-log-analyzer]

The job x86_64-msvc failed! Check out the build log: (web) (plain)

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

warning: [email protected]: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 60.673
[RUSTC-TIMING] coretests test:true 88.878
Build completed unsuccessfully in 0:54:54
make: *** [Makefile:102: ci-msvc-ps1] Error 1
  network time: Wed, 04 Sep 2024 09:33:46 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

[bors]

💔 Test failed - checks-actions

[lqd]

again, failed to remove file C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-std\x86_64-pc-windows-msvc\release\deps\libcompiler_builtins-7c3f7c6358f370a6.rlib

@bors retry

[bors]

⌛ Testing commit 6aeb9b4 with merge ffa0d7e...

[rust-log-analyzer]

The job x86_64-msvc failed! Check out the build log: (web) (plain)

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

warning: [email protected]: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 61.536
[RUSTC-TIMING] coretests test:true 89.093
Build completed unsuccessfully in 0:54:34
make: *** [Makefile:102: ci-msvc-ps1] Error 1
  network time: Wed, 04 Sep 2024 12:16:47 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

[bors]

💔 Test failed - checks-actions

[tgross35]

failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-std\x86_64-pc-windows-msvc\release\deps\libcompiler_builtins-7c3f7c6358f370a6.rlib #127883

@bors retry

[bors]

⌛ Testing commit 6aeb9b4 with merge aa44b01...

[rust-log-analyzer]

The job x86_64-msvc failed! Check out the build log: (web) (plain)

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

warning: [email protected]: 1 warning generated.
[RUSTC-TIMING] corebenches test:true 59.708
[RUSTC-TIMING] coretests test:true 87.816
Build completed unsuccessfully in 0:53:57
make: *** [Makefile:102: ci-msvc-ps1] Error 1
  network time: Thu, 05 Sep 2024 02:39:54 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

[bors]

💔 Test failed - checks-actions

[tgross35]

@bors retry

[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-352zljc (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-352zljc --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

Auto-merging src/librustdoc/html/static/js/main.js
Auto-merging src/librustdoc/html/static/css/rustdoc.css
Auto-merging src/librustdoc/html/render/sidebar.rs
CONFLICT (content): Merge conflict in src/librustdoc/html/render/sidebar.rs
Automatic merge failed; fix conflicts and then commit the result.