Duncan P. N. Exon Smith 83533dd617 LTO: Check local linkage first ... Since visibility is meaningless for symbols with local linkage, check local linkage before visibility when setting symbol attributes. When linkage is `internal` and the visibility is `hidden`, the exposed attribute is now `LTO_SYMBOL_SCOPE_INTERNAL` instead of `LTO_SYMBOL_SCOPE_HIDDEN`. Although the bitfield allows *both* to be specified, the combination is nonsense anyway. Given changes (in progress) to drop visibility when a symbol has local linkage, this almost has no functionality change: it's mostly a cleanup to clarify the logic. The exception is when something has `appending` linkage. Before this change, such symbols would be advertised as `LTO_SYMBOL_SCOPE_INTERNAL`; now, they'll be given `LTO_SYMBOL_SCOPE_COMMON`. Unfortunately this is really awkward to test. This only changes what we advertise to linkers (before running LTO), not what the final object looks like. In theory I could add `DEBUG` output to `llvm-lto` (and test with "REQUIRES: asserts"), but follow-up commits to disallow `internal hidden` simplify this anyway. <rdar://problem/16141113> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@208261 91177308-0d34-0410-b5e6-96231b3b80d8		2014-05-07 22:53:14 +00:00
..
CMakeLists.txt
LLVMBuild.txt	Prune redundant dependencies in LLVMBuild.txt.	2013-12-11 00:30:57 +00:00
LTOCodeGenerator.cpp	Use a range loop.	2014-05-05 20:06:41 +00:00
LTOModule.cpp	LTO: Check local linkage first	2014-05-07 22:53:14 +00:00
Makefile	Test commit. Fixed a copy-paste error in the Makefile for lib/LTO.	2013-10-03 18:05:12 +00:00