forked from OSchip/llvm-project
c0cd1f1c5c
This simplifies a lot of handling of BoolAttr/IntegerAttr. For example, a lot of places currently have to handle both IntegerAttr and BoolAttr. In other places, a decision is made to pick one which can lead to surprising results for users. For example, DenseElementsAttr currently uses BoolAttr for i1 even if the user initialized it with an Array of i1 IntegerAttrs. Differential Revision: https://reviews.llvm.org/D81047 |
||
---|---|---|
.. | ||
LLVMIR | ||
CMakeLists.txt |