aboutsummaryrefslogtreecommitdiff
path: root/clang/tools/clang-format/clang-format-diff.py
diff options
context:
space:
mode:
authorjeanPerier <jperier@nvidia.com>2024-08-27 11:05:13 +0200
committerGitHub <noreply@github.com>2024-08-27 11:05:13 +0200
commit0ea0ecd64f54e307670b860b309d2e869c1de3d1 (patch)
tree4957282e7ace1cd30d695965950850558d61383a /clang/tools/clang-format/clang-format-diff.py
parentd4f97da13218bf5d21b3aebb358e8799b3cdae73 (diff)
downloadllvm-0ea0ecd64f54e307670b860b309d2e869c1de3d1.zip
llvm-0ea0ecd64f54e307670b860b309d2e869c1de3d1.tar.gz
llvm-0ea0ecd64f54e307670b860b309d2e869c1de3d1.tar.bz2
[flang][driver] apply mlir pass options immediately after lowering (#106099)
The verification pass is run right after lowering with its own pass manager by flang driver, but the mlir command line options were not applied to this pass manager. This prevented options like `-mmlir --mlir-pass-pipeline-crash-reproducer="crash.fir"` or `-mmlir --mlir-print-ir-after-failure` to work when a verifier error was hit right after lowering, while these options are useful to investigate/reproduce internal errors. Note that the change in the pipeline tests is not showing a new pass being run: the pass was already run, but `-mmlir --mlir-pass-statistics` was not applied when the initial verification pass was run. Note that when we deal with compiler performance, we will probably want to run the verification pass only once after the initial lowering (this patch shows that it is called twice in a raw: once after the initial lowering, once at the beginning of FIR to LLVM IR lowering).
Diffstat (limited to 'clang/tools/clang-format/clang-format-diff.py')
0 files changed, 0 insertions, 0 deletions