Peter Collingbourne 3d7ffbad08 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
..
gold	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
llvm-cov	llvm-cov: Push some more debug output into the View (NFC)	2014-09-17 21:48:52 +00:00
llvm-lit	[tests] Cleanup initialization of test suffixes.	2013-08-16 00:37:11 +00:00
llvm-objdump	[llvm-objdump] clean up test cases now that build bots are green	2014-09-17 21:53:07 +00:00
llvm-profdata	llvm-profdata: Avoid undefined behaviour when reading raw profiles	2014-09-12 21:22:55 +00:00
llvm-readobj	yaml2obj: Support bigobj	2014-09-16 03:52:46 +00:00
llvm-vtabledump	llvm-vtabledump: A vtable dumper	2014-07-24 23:14:40 +00:00