ValueMapper: Always use Mapper::mapValue from remapInstruction, NFCI

Use Mapper::mapValue instead of llvm::MapValue from
Mapper::remapInstruction when mapping an incoming block for a PHINode
(follow-up to r265832).  This will implicitly pass along the
Materializer argument, but when this code was added in r133513 there was
no Materializer argument.  I suspect this call to MapValue was just
missed in r182776 since it's not observable (basic blocks can't be
materialized, and they don't reference other values).

llvm-svn: 265833
This commit is contained in:
Duncan P. N. Exon Smith 2016-04-08 19:17:13 +00:00
parent a574e7a7a4
commit adcebdf2d1
1 changed files with 1 additions and 2 deletions

View File

@ -757,8 +757,7 @@ void Mapper::remapInstruction(Instruction *I) {
// Remap phi nodes' incoming blocks.
if (PHINode *PN = dyn_cast<PHINode>(I)) {
for (unsigned i = 0, e = PN->getNumIncomingValues(); i != e; ++i) {
// FIXME: Use Mapper::mapValue (but note the missing Materializer flag).
Value *V = MapValue(PN->getIncomingBlock(i), VM, Flags);
Value *V = mapValue(PN->getIncomingBlock(i));
// If we aren't ignoring missing entries, assert that something happened.
if (V)
PN->setIncomingBlock(i, cast<BasicBlock>(V));