diff options
| author | Sanjay Patel <spatel@rotateright.com> | 2018-08-02 13:46:20 +0000 |
|---|---|---|
| committer | Sanjay Patel <spatel@rotateright.com> | 2018-08-02 13:46:20 +0000 |
| commit | f9a0d593e9da6d7d16ae2f5b073eb6598bc35875 (patch) | |
| tree | 431bb60d541f1fbf347705679c58f119f2a17171 /lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp | |
| parent | 1f3977a856a3313a028a2505ec9a59950204a5a1 (diff) | |
| download | bcm5719-llvm-f9a0d593e9da6d7d16ae2f5b073eb6598bc35875.tar.gz bcm5719-llvm-f9a0d593e9da6d7d16ae2f5b073eb6598bc35875.zip | |
[ValueTracking] fix maxnum miscompile for cannotBeOrderedLessThanZero (PR37776)
This adds the NAN checks suggested in PR37776:
https://bugs.llvm.org/show_bug.cgi?id=37776
If both operands to maxnum are NAN, that should get constant folded, so we don't
have to handle that case. This is the same assumption as other FP ops in this
function. Returning 'false' is always conservatively correct.
Copying from the bug report:
Currently, we have this for "when is cannotBeOrderedLessThanZero
(mustBePositiveOrNaN) true for maxnum":
L
-------------------
| Pos | Neg | NaN |
------------------------
|Pos | x | x | x |
------------------------
R |Neg | x | | x |
------------------------
|NaN | x | x | x |
------------------------
The cases with (Neg & NaN) are wrong. We should have:
L
-------------------
| Pos | Neg | NaN |
------------------------
|Pos | x | x | x |
------------------------
R |Neg | x | | |
------------------------
|NaN | x | | x |
------------------------
Differential Revision: https://reviews.llvm.org/D50081
llvm-svn: 338716
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp')
0 files changed, 0 insertions, 0 deletions
