Bill Wendling 37b94c6b4e If the global variable is removed by the linker, then don't constant merge it ... with other symbols. An object in the __cfstring section is suppoed to be filled with CFString objects, which have a pointer to ___CFConstantStringClassReference followed by a pointer to a __cstring. If we allow the object in the __cstring section to be merged with another global, then it could end up in any section. Because the linker is going to remove these symbols in the final executable, we shouldn't bother to merge them. <rdar://problem/10564621> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@147899 91177308-0d34-0410-b5e6-96231b3b80d8		2012-01-11 00:13:08 +00:00
..
2002-09-23-CPR-Update.ll
2003-10-28-MergeExternalConstants.ll
2011-01-15-EitherOrder.ll	Don't merge two constants if we care about the address of both.	2011-01-16 17:05:09 +00:00
dg.exp
dont-merge.ll	fix PR8144, a bug where constant merge would merge globals marked	2010-09-15 00:30:11 +00:00
linker-private.ll	If the global variable is removed by the linker, then don't constant merge it	2012-01-11 00:13:08 +00:00
merge-both.ll	Teach the ConstantMerge pass about alignment. Fixes PR10514!	2011-07-27 19:47:34 +00:00
unnamed-addr.ll	Don't merge two constants if we care about the address of both.	2011-01-16 17:05:09 +00:00