diff options
| author | River Riddle <riddleriver@gmail.com> | 2022-02-13 23:51:46 -0800 |
|---|---|---|
| committer | River Riddle <riddleriver@gmail.com> | 2022-02-26 11:08:51 -0800 |
| commit | a486cf5e98bcf6a186bf3d01ba4539a3e27bd08d (patch) | |
| tree | 97ec6cefc6c1ab0cd8f399de07d84e180e7d0d31 /llvm/unittests/Support/UnicodeTest.cpp | |
| parent | 95b4e88b1db348fbb074c945bd85c777cf807cc0 (diff) | |
| download | llvm-a486cf5e98bcf6a186bf3d01ba4539a3e27bd08d.zip llvm-a486cf5e98bcf6a186bf3d01ba4539a3e27bd08d.tar.gz llvm-a486cf5e98bcf6a186bf3d01ba4539a3e27bd08d.tar.bz2 | |
[mlir:PDLL] Fix handling of unspecified operands/results on operation expressions
If the operand list or result list of an operation expression is not specified, we interpret
this as meaning that the operands/results are "unconstraint" (i.e. "could be anything").
We currently don't properly handle differentiating this case from the case of
"no operands/results". This commit adds the insertion of implicit value/type range
variables when these lists are unspecified. This allows for adding proper support
for when zero operands or results are expected.
Differential Revision: https://reviews.llvm.org/D119780
Diffstat (limited to 'llvm/unittests/Support/UnicodeTest.cpp')
0 files changed, 0 insertions, 0 deletions