summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp
diff options
context:
space:
mode:
authorMichael Kruse <llvm@meinersbur.de>2017-03-09 22:29:58 +0000
committerMichael Kruse <llvm@meinersbur.de>2017-03-09 22:29:58 +0000
commite4292bf08660b2e945d68dd7c9918620ec25cf8a (patch)
tree4587bb742240c5d3a438ea0163d3ae9f4f0fdd41 /llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp
parent544210304fbae675632c5a5bc54c7fa5b441f670 (diff)
downloadbcm5719-llvm-e4292bf08660b2e945d68dd7c9918620ec25cf8a.tar.gz
bcm5719-llvm-e4292bf08660b2e945d68dd7c9918620ec25cf8a.zip
[Support] Add -polly-dump-module pass.
This pass allows writing the LLVM-IR just before and after the Polly passes to a file. Dumping the IR before Polly helps reproducing bugs that occur in code generated by clang. It is the only reliable way to get the IR that triggers a bug. The alternative is to emit the IR with clang -c -emit-llvm -S -o dump.ll then pass it through all optimization passes opt dump.ll -basicaa -sroa ... -S -o optdump.ll to then reproduce the error with opt optdump.ll -polly-opt-isl -polly-codegen -analyze However, the IR is not the same. -O3 uses a PassBuilder than creates passes with different parameters than the default. Dumping the IR after Polly is useful to compare a miscompilation with a known-good configuration. Differential Revision: https://reviews.llvm.org/D30788 llvm-svn: 297415
Diffstat (limited to 'llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud