mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-19 19:12:56 +02:00
[SelectionDAG] Dump the DAG after legalizing vector ops and after the second type legalization
Summary: With -debug, we aren't dumping the DAG after legalizing vector ops. In particular, on X86 with AVX1 only, we don't dump the DAG after we split 256-bit integer ops into pairs of 128-bit ADDs since this occurs during vector legalization. I'm only dumping if the legalize vector ops changes something since we don't print anything during legalize vector ops. So this dump shows up right after the first type-legalization dump happens. So if nothing changed this second dump is unnecessary. Having said that though, I think we should probably fix legalize vector ops to log what its doing. Reviewers: RKSimon, eli.friedman, spatel, arsenm, chandlerc Reviewed By: RKSimon Subscribers: wdng, llvm-commits Differential Revision: https://reviews.llvm.org/D29554 llvm-svn: 294711
This commit is contained in:
parent
105c1f8b7f
commit
eef1a7854a
@ -834,12 +834,18 @@ void SelectionDAGISel::CodeGenAndEmitDAG() {
|
||||
}
|
||||
|
||||
if (Changed) {
|
||||
DEBUG(dbgs() << "Vector-legalized selection DAG: BB#" << BlockNumber
|
||||
<< " '" << BlockName << "'\n"; CurDAG->dump());
|
||||
|
||||
{
|
||||
NamedRegionTimer T("legalize_types2", "Type Legalization 2", GroupName,
|
||||
GroupDescription, TimePassesIsEnabled);
|
||||
CurDAG->LegalizeTypes();
|
||||
}
|
||||
|
||||
DEBUG(dbgs() << "Vector/type-legalized selection DAG: BB#" << BlockNumber
|
||||
<< " '" << BlockName << "'\n"; CurDAG->dump());
|
||||
|
||||
if (ViewDAGCombineLT && MatchFilterBB)
|
||||
CurDAG->viewGraph("dag-combine-lv input for " + BlockName);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user