llvm/jumptable.ll at e8c6bd7d9b334ddbd453e6845870d06c0a71076d - llvm - Gitea: Git with a cup of tea

RPCS3/llvm

mirror of https://github.com/RPCS3/llvm.git synced 2024-11-30 15:10:30 +00:00

Chandler Carruth 840b5d58c3 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.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@214287 91177308-0d34-0410-b5e6-96231b3b80d8

2014-07-30 05:44:04 +00:00

9 lines

177 B

LLVM

Raw Blame History

 ; RUN: not llvm-as -disable-output %s 2>&1 | FileCheck %s
 define i32 @f() jumptable {
   ret i32 0
 }
 ; CHECK: Attribute 'jumptable' requires 'unnamed_addr'
 ; CHECK: i32 ()* @f