diff options
| author | Craig Topper <craig.topper@intel.com> | 2018-02-08 18:55:14 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2018-02-08 18:55:14 +0000 |
| commit | 9b611e436fbf9f973bb154da477463ae8e8a2c52 (patch) | |
| tree | c9817972e40125d0eb6cc2167e27fc3ff32828be /lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp | |
| parent | 08d829da3e92f193335e999da331e0f9945d4003 (diff) | |
| download | bcm5719-llvm-9b611e436fbf9f973bb154da477463ae8e8a2c52.tar.gz bcm5719-llvm-9b611e436fbf9f973bb154da477463ae8e8a2c52.zip | |
[SelectionDAG] Add a helper function for creating a boolean constant based on the target's boolean content
Many in SimplifySetCC and FoldSetCC try to create true or false constants. Some of them query getBooleanContents to figure out whether to use all ones or just 1 for true. But many places do not check and just use 1 without ensuring the VT has an i1 scalar type. Note sure if those places only trigger before type legalization so they only see an i1
type?
To cleanup the inconsistency and reduce some duplicated code, this patch adds a getBoolConstant method to SelectionDAG that takes are of querying getBooleanContents and doing the right thing.
Differential Revision: https://reviews.llvm.org/D43037
llvm-svn: 324634
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp')
0 files changed, 0 insertions, 0 deletions
