summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2014-07-30 05:44:04 +0000
committerChandler Carruth <chandlerc@gmail.com>2014-07-30 05:44:04 +0000
commit681069d6754c329e854facf2f095cd5dbb474e30 (patch)
treec199ca05478050ccc5389aa5119688be7a9c6223 /llvm/lib/CodeGen
parenteaa88c1eee7211826bed26953808e08447cf89e4 (diff)
downloadbcm5719-llvm-681069d6754c329e854facf2f095cd5dbb474e30.tar.gz
bcm5719-llvm-681069d6754c329e854facf2f095cd5dbb474e30.zip
Don't manually (and forcibly) run the verifier on the entire module from
the jump instruction table pass. First, the verifier is already built into all the tools. The test case is adapted to just run llvm-as demonstrating that we still catch the broken module. Second, the verifier is *extremely* slow. This was responsible for very significant compile time regressions. If you have deployed a Clang binary anywhere from r210280 to this commit, you really want to re-deploy. llvm-svn: 214287
Diffstat (limited to 'llvm/lib/CodeGen')
-rw-r--r--llvm/lib/CodeGen/JumpInstrTables.cpp4
1 files changed, 0 insertions, 4 deletions
diff --git a/llvm/lib/CodeGen/JumpInstrTables.cpp b/llvm/lib/CodeGen/JumpInstrTables.cpp
index 61ef722dce5..750f71f6022 100644
--- a/llvm/lib/CodeGen/JumpInstrTables.cpp
+++ b/llvm/lib/CodeGen/JumpInstrTables.cpp
@@ -251,10 +251,6 @@ FunctionType *JumpInstrTables::transformType(FunctionType *FunTy) {
}
bool JumpInstrTables::runOnModule(Module &M) {
- // Make sure the module is well-formed, especially with respect to jumptable.
- if (verifyModule(M))
- return false;
-
JITI = &getAnalysis<JumpInstrTableInfo>();
// Get the set of jumptable-annotated functions.
OpenPOWER on IntegriCloud