projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 75f10c9) | patch
[TargetLowering] Use getBoolConstant instead of assuming zero or one for boolean...
authorCraig Topper <craig.topper@sifive.com>
Fri, 22 Jan 2021 08:19:13 +0000 (00:19 -0800)
committerCraig Topper <craig.topper@sifive.com>
Fri, 22 Jan 2021 08:26:14 +0000 (00:26 -0800)
commitc953a8334707951d172e8061c8dc9054eb0c5c3f
tree4c48cc3b6457f6caae61f1fd560a21f15c61cea5tree | snapshot
parent75f10c957477b269d9b954a686231342aeb8004bcommit | diff
[TargetLowering] Use getBoolConstant instead of assuming zero or one for boolean contents.

Noticed while I was touching other nearby code. I don't have a
test where this matters because the targets I work on
use zero or one boolean contents. And the tests cases I've seen
this fire on happen before type legalization where the result type
is MVT::i1 so the distinction doesn't matter.
llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp diff | blob | history
Domain: System / Toolchain;