| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
it comes back, it will be largely a rewrite, so keeping the old codebase
in tree isn't helping anyone.
llvm-svn: 116190
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fix: add a flag to MapValue and friends which indicates whether
any module-level mappings are being made. In the common case of
inlining, no module-level mappings are needed, so MapValue doesn't
need to examine non-function-local metadata, which can be very
expensive in the case of a large module with really deep metadata
(e.g. a large C++ program compiled with -g).
This flag is a little awkward; perhaps eventually it can be moved
into the ClonedCodeInfo class.
llvm-svn: 112190
|
|
|
|
|
|
| |
The ValueMapper used by various cloning utility maps MDNodes also.
llvm-svn: 106706
|
|
|
|
| |
llvm-svn: 101334
|
|
|
|
|
|
| |
present in the module.
llvm-svn: 97232
|
|
|
|
| |
llvm-svn: 97228
|
|
|
|
| |
llvm-svn: 97220
|
|
|
|
|
|
|
|
| |
object construction. There is no provision to change them when the
code for a function generated.
So we have to change these names while printing assembly.
llvm-svn: 97213
|
|
|
|
| |
llvm-svn: 96591
|
|
|
|
| |
llvm-svn: 96589
|
|
|
|
|
|
| |
cloned functions.
llvm-svn: 96485
|
|
|
|
|
|
| |
with mangled names).
llvm-svn: 96465
|
|
This pass is supposed to be run on the linked .bc module.
It traveses the module call graph twice. Once starting from the main function
and marking each reached function as "ML". Again, starting from the ISR
and cloning any reachable function that was marked as "ML". After cloning
the function, it remaps all the call sites in IL functions to call the
cloned functions.
Currently only marking is being done.
llvm-svn: 96435
|