aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-readobj/llvm-readobj.cpp
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2015-09-08 23:28:38 +0000
committerReid Kleckner <rnk@google.com>2015-09-08 23:28:38 +0000
commit51189f0a1d0b8b6d1490a4e42df4971916fb9235 (patch)
tree804c110f1c9172e760631974831c8fd1dd52a950 /llvm/tools/llvm-readobj/llvm-readobj.cpp
parenta195adde001abe1b337a4455b8b8c80f340f8a2e (diff)
downloadllvm-51189f0a1d0b8b6d1490a4e42df4971916fb9235.zip
llvm-51189f0a1d0b8b6d1490a4e42df4971916fb9235.tar.gz
llvm-51189f0a1d0b8b6d1490a4e42df4971916fb9235.tar.bz2
[WinEH] Avoid creating MBBs for LLVM BBs that cannot contain code
Typically these are catchpads, which hold data used to decide whether to catch the exception or continue unwinding. We also shouldn't create MBBs for catchendpads, cleanupendpads, or terminatepads, since no real code can live in them. This fixes a problem where MI passes (like the register allocator) would try to put code into catchpad blocks, which are not executed by the runtime. In the new world, blocks ending in invokes now have many possible successors. llvm-svn: 247102
Diffstat (limited to 'llvm/tools/llvm-readobj/llvm-readobj.cpp')
0 files changed, 0 insertions, 0 deletions