diff options
| author | PiJoules <6019989+PiJoules@users.noreply.github.com> | 2025-10-15 11:23:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-15 18:23:33 +0000 |
| commit | bd6ed29f342ef273ead8f4d57a0cd4e95e0a6354 (patch) | |
| tree | dd65935663b2cbbc2c0c215c0615b7168c6484fb /lldb/packages/Python/lldbsuite/test/gdbclientutils.py | |
| parent | 1673501fe5df963dbb0efec355d04c7fd8716347 (diff) | |
| download | llvm-bd6ed29f342ef273ead8f4d57a0cd4e95e0a6354.zip llvm-bd6ed29f342ef273ead8f4d57a0cd4e95e0a6354.tar.gz llvm-bd6ed29f342ef273ead8f4d57a0cd4e95e0a6354.tar.bz2 | |
[X86] Do not use movq in -mcmodel=kernel on an out of range abs global (#163323)
CFI can lead to some `relocation R_X86_64_32S out of range` errors when
using thinlto. We have an instance of an `inline_bits` alias with a
value of 0x8000008000000001 which cannot fit into a signed 32-bit reloc
hence the error. This reloc is used because the instruction for reading
the alias is `movq` which uses a signed 32-bit immediate. The proper
instruction to use in this instance is `movabs` for the full 64-bit
reloc.
Under the kernel model, a signed 32-bit immediate was always used but if
the target is a global with `absolue_symbol` we should reject the
MOV64ri32. The pattern matching logic will eventually lead to a match for
MOV64ri which emits the `movabs`.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions