diff options
| author | wanglei <wanglei@loongson.cn> | 2024-05-16 17:15:21 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-16 17:15:21 +0800 |
| commit | 70608c24fae8943cb93276db4d0358722705507b (patch) | |
| tree | 37bdf4e8236b77de69c8ae4ae93a5dba8fd11214 /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | 30410018d32b2cc19552c6d6a3b7b6de84d99382 (diff) | |
| download | llvm-70608c24fae8943cb93276db4d0358722705507b.zip llvm-70608c24fae8943cb93276db4d0358722705507b.tar.gz llvm-70608c24fae8943cb93276db4d0358722705507b.tar.bz2 | |
[LoongArch] Refactor LoongArchABI::computeTargetABI
The previous logic did not consider whether the architectural features
meet the requirements of the ABI, resulting in the generation of
incorrect object files in some cases. For example:
```
llc -mtriple=loongarch64 -filetype=obj test/CodeGen/LoongArch/ir-instruction/fadd.ll -o t.o
llvm-readelf -h t.o
```
The object file indicates the ABI as lp64d, however, the generated code
is lp64s.
The new logic introduces the `feature-implied` ABI. When both target-abi
and triple-implied ABI are invalid, the feature-implied ABI is used.
Reviewed By: SixWeining, xen0n
Pull Request: https://github.com/llvm/llvm-project/pull/92223
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions