diff options
| author | Sanjay Patel <spatel@rotateright.com> | 2021-01-27 14:11:22 -0500 |
|---|---|---|
| committer | Sanjay Patel <spatel@rotateright.com> | 2021-01-27 14:17:11 -0500 |
| commit | ab93c18c125f0ee51959ef225fa8f09f4dc29e35 (patch) | |
| tree | bb99e18f1b022770b67478730bca9332cea23f40 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | d90bb66dd931a45cae3399dc76942bf8e412fa7b (diff) | |
| download | llvm-ab93c18c125f0ee51959ef225fa8f09f4dc29e35.zip llvm-ab93c18c125f0ee51959ef225fa8f09f4dc29e35.tar.gz llvm-ab93c18c125f0ee51959ef225fa8f09f4dc29e35.tar.bz2 | |
[LoopVectorize] use IR fast-math-flags exclusively (not FP function attributes)
I am trying to untangle the fast-math-flags propagation logic
in the vectorizers (see a6f022127 for SLP).
The loop vectorizer has a mix of checking FP function attributes,
IR-level FMF, and just wrong assumptions.
I am trying to avoid regressions while fixing this, and I think
the IR-level logic is good enough for that, but it's hard to say
for sure. This would be the 1st step in the clean-up.
The existing test that I changed to include 'fast' actually shows
a miscompile: the function only had the equivalent of nnan, but we
created new instructions that had fast (all FMF set). This is
similar to the example in https://llvm.org/PR35538
Differential Revision: https://reviews.llvm.org/D95452
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
