aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CIR/CodeGen/CIRGenModule.cpp
diff options
context:
space:
mode:
authorMin-Yih Hsu <min.hsu@sifive.com>2025-04-08 10:31:05 -0700
committerGitHub <noreply@github.com>2025-04-08 10:31:05 -0700
commit9bfb4b8fb194c1df5b082888abc03d095e39b6e9 (patch)
tree828f69446d8f1173c75392ea81d4f871602af384 /clang/lib/CIR/CodeGen/CIRGenModule.cpp
parentb7b3758e88f15a7ec27f212cd46e3dcf4e2f39f5 (diff)
downloadllvm-9bfb4b8fb194c1df5b082888abc03d095e39b6e9.zip
llvm-9bfb4b8fb194c1df5b082888abc03d095e39b6e9.tar.gz
llvm-9bfb4b8fb194c1df5b082888abc03d095e39b6e9.tar.bz2
[MachineScheduler] Add more debug prints w.r.t hazards and pending SUnits (#134328)
While we already have some detailed debug messages on the candidate selection process -- which selects a SUnit from the Available queue, we didn't say much about why a SUnit was _not_ moved from Pending queue to Available queue in the first place, which is just as important as why we scheduled a node IMHO. Therefore, I added some debug prints for this very purpose. I decide to print these extra messages by default (instead of being guarded by command line like `-misched-detail-resource-booking`) because we have been printing some of the hazard remarks, so I thought we might as well print these new messages -- which are mostly about hazard -- by default.
Diffstat (limited to 'clang/lib/CIR/CodeGen/CIRGenModule.cpp')
0 files changed, 0 insertions, 0 deletions