diff options
| author | YunQiang Su <yunqiang@isrc.iscas.ac.cn> | 2024-10-10 15:09:47 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-10 15:09:47 +0800 |
| commit | 8d35ab80fc7a856ac6a60cf9074210f3983206ac (patch) | |
| tree | dff0235dbf39ac6e8c4bae2d068c32680b89c2ec /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | f93258e4aca518cba3d48db59ed6143ca19ca99b (diff) | |
| download | llvm-8d35ab80fc7a856ac6a60cf9074210f3983206ac.zip llvm-8d35ab80fc7a856ac6a60cf9074210f3983206ac.tar.gz llvm-8d35ab80fc7a856ac6a60cf9074210f3983206ac.tar.bz2 | |
AArch64: Add FMINNUM_IEEE and FMAXNUM_IEEE support (#107855)
FMINNM/FMAXNM instructions of AArch64 follow IEEE754-2008. We can use
them to canonicalize a floating point number. And
FMINNUM_IEEE/FMAXNUM_IEEE is used by something like expanding
FMINIMUMNUM/FMAXIMUMNUM, so let's define them.
Update combine_andor_with_cmps.ll.
Add fp-maximumnum-minimumnum.ll, with nnan testcases only.
V1F64 is not supported yet.
If we set v1f64 as legal, FMINNUM/FMAXNUM will have some problem:
both of them use `if (isOperationLegalOrCustom(FMAXNUM_IEEE, VT))`.
AArch64 depends on `expandFMINNUM_FMAXNUM` returning `SDValue()`
for FMAXNUM and FMINNUM.
We should fix this problem, while it will be in future patch.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions