about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2025-04-06 16:21:03 +1000
committerGitHub <noreply@github.com>2025-04-06 16:21:03 +1000
commitf4aa209e206788a7c75ef3484e98092872864e51 (patch)
treef05eaf76707f66ddbfbd50ab0eebb94e0bf0a7ee /compiler/rustc_codegen_llvm/src
parentf55034b2ebfb14c1748f30c25814e442727ee79e (diff)
parentf6afb35c6170ad3cadc6e6d7d41dc4dc3bd46556 (diff)
downloadrust-f4aa209e206788a7c75ef3484e98092872864e51.tar.gz
rust-f4aa209e206788a7c75ef3484e98092872864e51.zip
Rollup merge of #139438 - Zalathar:fix-test-122600, r=scottmcm
Prevent a test from seeing forbidden numbers in the rustc version

The final CHECK-NOT directive in this test was able to see past the end of the enclosing function, and find the substring `753` or `754` in the git hash in the rustc version number, causing false failures in CI whenever the git hash happens to contain those digits in sequence.

Adding an explicit check for `ret` prevents the CHECK-NOT directive from seeing past the end of the function.

---

Manually tested by adding `// CHECK-NOT: rustc` after the existing CHECK-NOT directives, and demonstrating that the new check prevents it from seeing the rustc version string.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions