Peter Collingbourne 10039c02ea LTO: introduce object file-based on-disk module format. ... This format is simply a regular object file with the bitcode stored in a section named ".llvmbc", plus any number of other (non-allocated) sections. One immediate use case for this is to accommodate compilation processes which expect the object file to contain metadata in non-allocated sections, such as the ".go_export" section used by some Go compilers [1], although I imagine that in the future we could consider compiling parts of the module (such as large non-inlinable functions) directly into the object file to improve LTO efficiency. [1] http://golang.org/doc/install/gccgo#Imports Differential Revision: http://reviews.llvm.org/D4371 llvm-svn: 218078		2014-09-18 21:28:49 +00:00
..
alias-1.ll	Rewrite the gold plugin to fix pr19901.	2014-08-21 20:28:55 +00:00
bcsection.s	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
comdat.ll	Add support for comdats to the gold plugin.	2014-08-22 23:26:10 +00:00
common.ll	Handle common linkage correctly in the gold plugin.	2014-09-09 20:08:22 +00:00
invalid.bc	…
linker-script.export	…
pr19901-1.ll	Rewrite the gold plugin to fix pr19901.	2014-08-21 20:28:55 +00:00
weak.ll	Add a plugin testcase for merging weak variables.	2014-08-12 15:39:14 +00:00