diff options
| author | Roman Lebedev <lebedev.ri@gmail.com> | 2019-07-25 16:39:57 +0000 |
|---|---|---|
| committer | Roman Lebedev <lebedev.ri@gmail.com> | 2019-07-25 16:39:57 +0000 |
| commit | 8b65c4e331375c5c0508196b06821269df8b3f71 (patch) | |
| tree | 504f3c92d09a177cab73830c550b041406535d0a /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp | |
| parent | 8ee361ebe5ebada5c303b9aa93fecde9e4bec02a (diff) | |
| download | bcm5719-llvm-8b65c4e331375c5c0508196b06821269df8b3f71.tar.gz bcm5719-llvm-8b65c4e331375c5c0508196b06821269df8b3f71.zip | |
[NFC][CodeGen][X86][AArch64] div-rem pair reconstruction tests (PR42673)
As discussed in https://bugs.llvm.org/show_bug.cgi?id=42673
there is a TTI hook hasDivRemOp() that matters here.
While -div-rem-pairs will decompose 'rem' if that hook returns false,
nothing does the opposite transform.
We can't to this in InstCombine, because it does not currently
access TTI, and i'm not sure we should change that.
We may be able to teach DivRemPairs to do this, but this really is a
per-target perf optimization, and we seem to do the opposite transform
in backend if hasDivRemOp() returned false: https://godbolt.org/z/ttt4HZ
I think it makes sense to be consistent.
https://bugs.llvm.org/show_bug.cgi?id=42673
llvm-svn: 367034
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
