diff options
author | Wentao Zhang <35722712+whentojump@users.noreply.github.com> | 2024-02-22 16:04:25 -0600 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-02-22 16:04:25 -0600 |
commit | d4bfca3b2e673789f7c278d46a199ae8910ddd37 (patch) | |
tree | c1118b0e4ee9f669ab27136a34d9df434cf28606 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
parent | 72763521c34287bce68402eb2a9d71dcb4eed5a0 (diff) | |
download | llvm-d4bfca3b2e673789f7c278d46a199ae8910ddd37.zip llvm-d4bfca3b2e673789f7c278d46a199ae8910ddd37.tar.gz llvm-d4bfca3b2e673789f7c278d46a199ae8910ddd37.tar.bz2 |
[clang][CodeGen] Keep processing the rest of AST after encountering unsupported MC/DC expressions (#82464)
Currently, upon seeing unsupported decisions (more than 6 conditions, or
split nesting), the post-visitor hook dataTraverseStmtPost() returns a
false. As a result, in the rest of tree even supported decisions will
be skipped as well. Like in the below code:
{ // CompoundStmt
a && b; // 1: BinaryOperator (supported)
a && foo(b && c); // 2: BinaryOperator (not yet supported due to split
// nesting)
a && b; // 3: BinaryOperator (supported)
}
Decision 3 will not be processed at all. And only one "Decision" region
will be emitted. Compiler explorer example:
https://godbolt.org/z/Px61sesoo
We hope to process such cases and emit two "Decision" regions (1 and 3)
in the above example.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions