diff options
| author | Trevor Gross <t.gross35@gmail.com> | 2024-07-19 03:27:50 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-19 03:27:50 -0500 |
| commit | 6bdf9bd276b42ab10b14aff7dba0d2156bd2413d (patch) | |
| tree | 132bcad510fb5ad039dc8ed50e6d2ae3e081d6fc /compiler/rustc_codegen_llvm/src/llvm_util.rs | |
| parent | 0641b377473a0f9085353efe907656041dd39999 (diff) | |
| parent | 5686720a5706afa5628e1ff00cb6622eb1399d35 (diff) | |
| download | rust-6bdf9bd276b42ab10b14aff7dba0d2156bd2413d.tar.gz rust-6bdf9bd276b42ab10b14aff7dba0d2156bd2413d.zip | |
Rollup merge of #127935 - tgross35:binary_asm_labels-x86-only, r=estebank,Urgau
Change `binary_asm_labels` to only fire on x86 and x86_64 In <https://github.com/rust-lang/rust/pull/126922>, the `binary_asm_labels` lint was added which flags labels such as `0:` and `1:`. Before that change, LLVM was giving a confusing error on x86/x86_64 because of an incorrect interpretation. However, targets other than x86 and x86_64 never had the error message and have not been a problem. This means that the lint was causing code that previously worked to start failing (e.g. `compiler_builtins`), rather than only providing a more clear messages where there has always been an error. Adjust the lint to only fire on x86 and x86_64 assembly to avoid this regression. Also update the help message. Fixes: https://github.com/rust-lang/rust/issues/127821
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm_util.rs')
0 files changed, 0 insertions, 0 deletions