diff options
| author | Shengchen Kan <shengchen.kan@intel.com> | 2024-07-31 10:38:33 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-31 10:38:33 +0800 |
| commit | fd6faee5b3b5a7c0e5e87aa0b5719a1a48159ea0 (patch) | |
| tree | 248a0afc873c4d0cfd7b47bfd34cb2a0474ccacc /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 7231776a0218033ea81f73e69ca4bf66734d3117 (diff) | |
| download | llvm-fd6faee5b3b5a7c0e5e87aa0b5719a1a48159ea0.zip llvm-fd6faee5b3b5a7c0e5e87aa0b5719a1a48159ea0.tar.gz llvm-fd6faee5b3b5a7c0e5e87aa0b5719a1a48159ea0.tar.bz2 | |
[Driver,CodeGen] Report error when enabling 64-bit-only features on non-64-bit arch (#101151)
In front-end, now we detect for `-mapx-features=/-mapxf` and `-muintr`,
which is aligned with GCC
https://gcc.gnu.org/bugzilla/attachment.cgi?id=58698&action=diff
In backend, we just disable these 64-bit-only features silently, so that
there is no error for
`-march=native -m32` on APX-supported arch.
llvm-issue: https://github.com/llvm/llvm-project/issues/94810
GCC thread: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115978
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions