| commit | d2a074b1f463806a2c0e6a56b950a73635350fe7 | [log] [tgz] |
|---|---|---|
| author | David Majnemer <david.majnemer@gmail.com> | Fri Apr 29 18:40:34 2016 +0000 |
| committer | David Majnemer <david.majnemer@gmail.com> | Fri Apr 29 18:40:34 2016 +0000 |
| tree | d43d6d9933360a03eda503b86fdc0552a2581f15 | |
| parent | 10c4f451a8c0d96a83e31b309142f9f18e9a582d [diff] |
[ValueTracking] matchSelectPattern needs to be more careful around FP matchSelectPattern attempts to see through casts which mask min/max patterns from being more obvious. Under certain circumstances, it would misidentify a sequence of instructions as a min/max because it assumed that folding casts would preserve the result. This is not the case for floating point <-> integer casts. This fixes PR27575. llvm-svn: 268086