diff options
| author | Kito Cheng <kito.cheng@sifive.com> | 2021-04-06 09:09:55 +0800 |
|---|---|---|
| committer | Kito Cheng <kito.cheng@sifive.com> | 2022-01-29 00:01:00 +0800 |
| commit | a9d5bb926d45e9464d539226e380ae6accc95952 (patch) | |
| tree | d2437d83b5cbd139da4409b288c29dc7324d4052 /llvm/lib/Object/MachOObjectFile.cpp | |
| parent | 7d176844d05bf11b32c4379f1422379d3d979a1e (diff) | |
| download | llvm-a9d5bb926d45e9464d539226e380ae6accc95952.zip llvm-a9d5bb926d45e9464d539226e380ae6accc95952.tar.gz llvm-a9d5bb926d45e9464d539226e380ae6accc95952.tar.bz2 | |
[RISCV] Use __extendhfsf2/__truncsfhf2 for fp16 <-> fp32
`__gnu_h2f_ieee` and `__gnu_f2h_ieee` are introduce by ARM and set that as
default name for fp16 and fp32 conversion in LLVM.
However RISC-V GCC using default naming scheme for that, which is
`__extendhfsf2` and `__truncsfhf2` for that, that cause runtime ABI
incompatible issue.
Although we didn't have formal runtime ABI spec to specify those naming
convention yet, but I think it would be great to fix the incompatible
issue first.
And I've plan to create a runtime ABI spec undere psABI spec this year.
Reviewed By: asb
Differential Revision: https://reviews.llvm.org/D118207
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions