forked from OSchip/llvm-project
0fde00150d
and expose it as a utility class rather than as free function wrappers. The simple free-function interface works well for the bugpoint-specific pass's uses of code extraction, but in an upcoming patch for more advanced code extraction, they simply don't expose a rich enough interface. I need to expose various stages of the process of doing the code extraction and query information to decide whether or not to actually complete the extraction or give up. Rather than build up a new predicate model and pass that into these functions, just take the class that was actually implementing the functions and lift it up into a proper interface that can be used to perform code extraction. The interface is cleaned up and re-documented to work better in a header. It also is now setup to accept the blocks to be extracted in the constructor rather than in a method. In passing this essentially reverts my previous commit here exposing a block-level query for eligibility of extraction. That is no longer necessary with the more rich interface as clients can query the extraction object for eligibility directly. This will reduce the number of walks of the input basic block sequence by quite a bit which is useful if this enters the normal optimization pipeline. llvm-svn: 156163 |
||
|---|---|---|
| .. | ||
| bugpoint | ||
| bugpoint-passes | ||
| gold | ||
| llc | ||
| lli | ||
| llvm-ar | ||
| llvm-as | ||
| llvm-bcanalyzer | ||
| llvm-config | ||
| llvm-cov | ||
| llvm-diff | ||
| llvm-dis | ||
| llvm-dwarfdump | ||
| llvm-extract | ||
| llvm-link | ||
| llvm-mc | ||
| llvm-nm | ||
| llvm-objdump | ||
| llvm-prof | ||
| llvm-ranlib | ||
| llvm-readobj | ||
| llvm-rtdyld | ||
| llvm-shlib | ||
| llvm-size | ||
| llvm-stress | ||
| lto | ||
| macho-dump | ||
| opt | ||
| CMakeLists.txt | ||
| LLVMBuild.txt | ||
| Makefile | ||