llvm-svn: 123529

llvm-svn: 123364

1. Take a flags argument instead of a bool.  This makes
   it more clear to the reader what it is used for.
2. Add a flag that says that "remapping a value not in the
   map is ok".
3. Reimplement MapValue to share a bunch of code and be a lot
   more efficient.  For lookup failures, don't drop null values
   into the map.
4. Using the new flag a bunch of code can vaporize in LinkModules
   and LoopUnswitch, kill it.

No functionality change.

llvm-svn: 123058

llvm-svn: 122637

llvm-svn: 122636

llvm-svn: 122632

llvm-svn: 122158

llvm-svn: 122157

the buildbots.

llvm-svn: 122149

llvm-svn: 122142

llvm-svn: 122141

llvm-svn: 120298

llvm-svn: 116788

llvm-svn: 115827

fix is trying to accomplish.

This code could still use some polishing.

llvm-svn: 115759

source module *and* it must be merged (instead of simply replaced or appended
to), then merge instead of replacing or adding another global.

The ObjC __image_info section was being appended to because of this
failure. This caused a crash because the linker expects the image info section
to be a specific size.

<rdar://problem/8198537>

llvm-svn: 115753

llvm-svn: 112713

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

individual ...", which depends on r111922, which I am reverting.

llvm-svn: 112157

instructions, not when remapping modules.

llvm-svn: 112091

- Support the LinkerWeak*Linkage types in llvm-nm and in LinkModules.cpp.

llvm-svn: 111952

which reference GlobalValues are properly remapped.

llvm-svn: 111949

llvm-svn: 111948

which does the same thing. This eliminates redundant code and
handles MDNodes better. MDNode linking still doesn't fully
work yet though.

llvm-svn: 111941

llvm-svn: 111933

llvm-svn: 111102

llvm-svn: 111082

for creating and populating NamedMDNodes.

llvm-svn: 109061

llvm-svn: 107215

metadata types which should be marked as "weak", but which the linker will
remove upon final linkage. For example, the "objc_msgSend_fixup_alloc" symbol is
defined like this:

       .globl l_objc_msgSend_fixup_alloc
       .weak_definition l_objc_msgSend_fixup_alloc
       .section __DATA, __objc_msgrefs, coalesced
       .align 3
l_objc_msgSend_fixup_alloc:
        .quad   _objc_msgSend_fixup
        .quad   L_OBJC_METH_VAR_NAME_1

This is different from the "linker_private" linkage type, because it can't have
the metadata defined with ".weak_definition".

llvm-svn: 107205

methods to try to have the type predicates be more logically positioned.

llvm-svn: 96349

llvm-svn: 95468

Need to recurse for all operands of function-local metadata; and handle Instructions (which map to themselves)

llvm-svn: 94691

llvm-svn: 94650

llvm-svn: 94632

llvm-svn: 94243

Fixed linking of modules containing aliases to constant bitcasts.  Existing behaviour first tried to replace the aliases with the global that they aliased (rather than the bitcast), causing a crash on an assert because the types didn't match.  When this was fixed, it then did the same thing creating the new alias (creating an alias with a different type to its aliasee).  

Linking modules containing aliases to GEPs is still not quite right.  GEPs that are equivalent to bitcasts will be replaced by bitcasts, GEPs that are not will just break.  Aliases to GEPs that are not equivalent to bitcasts are horribly broken anyway (it might be worth adding an assert when creating the alias to prevent these being created; they just cause problems later).

llvm-svn: 93052

llvm-svn: 92628

things that occur in types.  "operands" are things that occur
in values.

llvm-svn: 92322

llvm-svn: 92192