summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
diff options
context:
space:
mode:
authorRoman Lebedev <lebedev.ri@gmail.com>2018-07-12 17:00:11 +0000
committerRoman Lebedev <lebedev.ri@gmail.com>2018-07-12 17:00:11 +0000
commit1574e49792cbbe0521ed62ec6c2a140b11a5bf99 (patch)
tree37e337813999f07b29586ce8077e09bf58a8c10b /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
parent0906a7fc53342cfb6869da2066274b03d7ceac9c (diff)
downloadbcm5719-llvm-1574e49792cbbe0521ed62ec6c2a140b11a5bf99.tar.gz
bcm5719-llvm-1574e49792cbbe0521ed62ec6c2a140b11a5bf99.zip
[NFC][X86][AArch64] Add tests for the 'check for [no] signed truncation' pattern
Summary: [[ https://bugs.llvm.org/show_bug.cgi?id=38149 | PR38149 ]] As discussed in https://reviews.llvm.org/D49179#1158957 and later, the IR can be improved: https://rise4fun.com/Alive/gBf ^ that pattern will be produced by Implicit Integer Truncation sanitizer, https://reviews.llvm.org/D48958 https://bugs.llvm.org/show_bug.cgi?id=21530 in signed case, therefore it is probably a good idea to improve it. But as it looks from these tests, i think we want to revert at least some cases in DAGCombine. Reviewers: spatel, craig.topper, RKSimon, javed.absar Reviewed By: spatel Subscribers: kristof.beyls, llvm-commits Differential Revision: https://reviews.llvm.org/D49247 llvm-svn: 336917
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud