RegionGenerator: Do not modify GlobalMaps
By inspection the update of the GlobalMaps in the RegionGenerator seems unneed, and is removed as also no test cases fail when dropping this. Johannes Doerfert confirmed that this is indeed save: "I think that code was needed when we did not use the scalar codegen by default. Now everything defined in a non-affine region should be communicated via memory and reloaded in the user block. Hence, we should be good removing this code." llvm-svn: 246926
This commit is contained in:
parent
113a4a4cbb
commit
8eae8361fc
|
@ -1039,11 +1039,6 @@ void RegionGenerator::copyStmt(ScopStmt &Stmt, LoopToScevMapT <S,
|
|||
LTS[L] = SE.getUnknown(LoopPHI);
|
||||
}
|
||||
|
||||
// Add all mappings from the region to the global map so outside uses will use
|
||||
// the copied instructions.
|
||||
for (auto &BBMap : RegionMaps)
|
||||
GlobalMap.insert(BBMap.second.begin(), BBMap.second.end());
|
||||
|
||||
// Reset the old insert point for the build.
|
||||
Builder.SetInsertPoint(ExitBBCopy->begin());
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue