mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-01-10 02:36:06 +00:00
Don't bother value numbering instructions with void types in GVN. In theory this should allow us to insert
fewer things into the value numbering maps, but any speedup is beneath the noise threshold on my machine on 403.gcc. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@122844 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
631ee4b89f
commit
2cf7537dc6
@ -1685,6 +1685,10 @@ bool GVN::processInstruction(Instruction *I,
|
||||
return false;
|
||||
}
|
||||
|
||||
// Instructions with void type don't return a value, so there's
|
||||
// no point in trying to find redudancies in them.
|
||||
if (I->getType()->isVoidTy()) return false;
|
||||
|
||||
uint32_t NextNum = VN.getNextUnusedValueNumber();
|
||||
unsigned Num = VN.lookup_or_add(I);
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user