aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetPassConfig.cpp
diff options
context:
space:
mode:
authorSam McCall <sam.mccall@gmail.com>2023-07-11 16:23:55 +0200
committerSam McCall <sam.mccall@gmail.com>2023-07-12 07:20:46 +0200
commitfa689726768b7b5cae01970cce2e59a72a0229b4 (patch)
tree0090dab35cfdc6cf999a9908e6e12f20bf9d00d7 /llvm/lib/CodeGen/TargetPassConfig.cpp
parent0bcef1d93de828950eef305640a0295f2181770a (diff)
downloadllvm-fa689726768b7b5cae01970cce2e59a72a0229b4.zip
llvm-fa689726768b7b5cae01970cce2e59a72a0229b4.tar.gz
llvm-fa689726768b7b5cae01970cce2e59a72a0229b4.tar.bz2
[dataflow] document flow condition
There's some documentation of this concept at https://clang.llvm.org/docs/DataFlowAnalysisIntro.html but it would be nice to have it closer to the code. I also was laboring under an obvious but wrong mental model that the flow condition token represented "execution reached this point", I'd like to explicitly call that out as wrong. Differential Revision: https://reviews.llvm.org/D154969
Diffstat (limited to 'llvm/lib/CodeGen/TargetPassConfig.cpp')
0 files changed, 0 insertions, 0 deletions