-
Notifications
You must be signed in to change notification settings - Fork 13.5k
inteldialect
does not handle labels 0:
or 1:
on x86
#99547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This reproduces in clang too with |
@llvm/issue-subscribers-backend-x86 Author: Trevor Gross (tgross35)
The below code:
define void @<!-- -->demo() {
start:
call void asm inteldialect "0: jmp 0b", ""()
ret void
} Should build. Instead, it provides an inaccurate error message:
This only happens on Link: https://llvm.godbolt.org/z/WWvWMzznK |
… the one provided with their repo is no longer able to build it (rust) due to a discovered bug in llvm (llvm/llvm-project#99547) - removed a no longer needed FIX for the build procedure of the synthetic-network docker image - retagging of the node-js local image
As triggered by the `binary_asm_labels` lint: error: avoid using labels containing only the digits `0` and `1` in inline assembly --> encapfn-mpk/src/lib.rs:1294:20 | 1294 | jz 100f // If zero, PKRU cleared correctly. | ____________________^ 1295 | | ud2 // If not zero, crash with an illegal insn 1296 | | 1297 | | 100: // _pkru_cleared | |_________________^ use a different label that doesn't start with `0` or `1` | = help: start numbering with `2` instead = note: an LLVM bug makes these labels ambiguous with a binary literal number on x86 = note: see <llvm/llvm-project#99547> for more information = note: `#[deny(binary_asm_labels)]` on by default
The below code:
Should build. Instead, it provides an inaccurate error message:
This only happens on
x86
andx86_64
, other platforms seem not to be affected. This looks like another case of #35492, cc @rnk who authored 953bdce.Link: https://llvm.godbolt.org/z/WWvWMzznK
Original repro: https://rust.godbolt.org/z/qP3Kd3Ts7
The text was updated successfully, but these errors were encountered: