llvm-mirror/tools/gold/CMakeLists.txt

set(LLVM_EXPORTED_SYMBOL_FILE ${CMAKE_CURRENT_SOURCE_DIR}/gold.exports)

if( LLVM_ENABLE_PIC AND LLVM_BINUTILS_INCDIR )
  include_directories( ${LLVM_BINUTILS_INCDIR} )

  # Because off_t is used in the public API, the largefile parts are required for
  # ABI compatibility.
  add_definitions( -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 )

  set(LLVM_LINK_COMPONENTS
     ${LLVM_TARGETS_TO_BUILD}
     Linker
     BitWriter
     IPO
     )

  add_llvm_loadable_module(LLVMgold
    gold-plugin.cpp
    )

endif()
EXPORTED_SYMBOL_FILE support for cmake The cmake build didn't support EXPORTED_SYMBOL_FILE. Instead, it had a Windows-only implementation in tools/lto/CMakeLists.txt, a linux-only implementation in tools/gold/CMakeLists.txt, and a darwin-only implementation in tools/clang/tools/libclang/CMakeLists.txt. This attempts to consolidate these one-offs into a single place. Clients can now just set LLVM_EXPORTED_SYMBOL_FILE and things (hopefully) Just Work, like in the make build. llvm-svn: 198136 2013-12-29 00:31:44 +01:00			`set(LLVM_EXPORTED_SYMBOL_FILE ${CMAKE_CURRENT_SOURCE_DIR}/gold.exports)`

Be less conservative about when we build the gold plugin. It is only build if LLVM_BINUTILS_INCDIR is explicitly given, so there is no point in having extra restrictions. llvm-svn: 223481 2014-12-05 18:25:52 +01:00			`if( LLVM_ENABLE_PIC AND LLVM_BINUTILS_INCDIR )`
Add LTO and gold plugin to the CMake build. Linux-only, support for other systems pending. PR9456. llvm-svn: 127466 2011-03-11 16:44:24 +01:00			`include_directories( ${LLVM_BINUTILS_INCDIR} )`

			`# Because off_t is used in the public API, the largefile parts are required for`
			`# ABI compatibility.`
			`add_definitions( -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 )`

Use lib/LTO directly in the gold plugin. The tools/lto API is not the best choice for implementing a gold plugin. Among other issues: * It is an stable ABI. Old errors stay and we have to be really careful before adding new features. * It has to support two fairly different linkers: gold and ld64. * We end up with a plugin that depends on a shared lib, something quiet unusual in LLVM land. * It hides LLVM. For some features in the gold plugin it would be really nice to be able to just get a Module or a GlobalValue. This change is intended to be a very direct translation from the C API. It will just enable other fixes and cleanups. Tested with a LTO bootstrap on linux. llvm-svn: 211315 2014-06-19 23:14:13 +02:00			`set(LLVM_LINK_COMPONENTS`
			`${LLVM_TARGETS_TO_BUILD}`
Rewrite the gold plugin to fix pr19901. There is a fundamental difference between how the gold API and lib/LTO view the LTO process. The gold API talks about a particular symbol in a particular file. The lib/LTO API talks about a symbol in the merged module. The merged module is then defined in terms of the IR semantics. In particular, a linkonce_odr GV is only copied if it is used, since it is valid to drop unused linkonce_odr GVs. In the testcase in pr19901 both properties collide. What happens is that gold asks us to keep a particular linkonce_odr symbol, but the IR linker doesn't copy it to the merged module and we never have a chance to ask lib/LTO to keep it. This patch fixes it by having a more direct implementation of the gold API. If it asks us to keep a symbol, we change the linkage so it is not linkonce. If it says we can drop a symbol, we do so. All of this before we even send the module to lib/Linker. Since now we don't have to produce LTO_SYMBOL_SCOPE_DEFAULT_CAN_BE_HIDDEN, during symbol resolution we can use a temporary LLVMContext and do lazy module loading. This allows us to keep the minimum possible amount of allocated memory around. This should also allow as much parallelism as we want, since there is no shared context. llvm-svn: 216215 2014-08-21 22:28:55 +02:00			`Linker`
			`BitWriter`
			`IPO`
Use lib/LTO directly in the gold plugin. The tools/lto API is not the best choice for implementing a gold plugin. Among other issues: * It is an stable ABI. Old errors stay and we have to be really careful before adding new features. * It has to support two fairly different linkers: gold and ld64. * We end up with a plugin that depends on a shared lib, something quiet unusual in LLVM land. * It hides LLVM. For some features in the gold plugin it would be really nice to be able to just get a Module or a GlobalValue. This change is intended to be a very direct translation from the C API. It will just enable other fixes and cleanups. Tested with a LTO bootstrap on linux. llvm-svn: 211315 2014-06-19 23:14:13 +02:00			`)`
Add LTO and gold plugin to the CMake build. Linux-only, support for other systems pending. PR9456. llvm-svn: 127466 2011-03-11 16:44:24 +01:00
			`add_llvm_loadable_module(LLVMgold`
			`gold-plugin.cpp`
			`)`
Restore the library dependency of LLVMgold on LTO; this was removed recently but is needed for LLVMgold to load in ld. llvm-svn: 198965 2014-01-10 23:48:35 +01:00
Fixing build break: should be in the if statement, not outside. llvm-svn: 198966 2014-01-10 23:55:25 +01:00			`endif()`