Peter Collingbourne 394be6c159 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 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@218078 91177308-0d34-0410-b5e6-96231b3b80d8		2014-09-18 21:28:49 +00:00
..
Archive.cpp	Don't own the buffer in object::Binary.	2014-08-19 18:44:46 +00:00
Binary.cpp	unique_ptrify MachOUniversalBinary::create	2014-09-03 17:41:05 +00:00
CMakeLists.txt
COFFObjectFile.cpp	Support: Delete {aligned_,}{u,}{little,big}8_t	2014-09-11 21:46:33 +00:00
COFFYAML.cpp
ELF.cpp
ELFObjectFile.cpp	Don't own the buffer in object::Binary.	2014-08-19 18:44:46 +00:00
ELFYAML.cpp
Error.cpp	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
IRObjectFile.cpp	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
LLVMBuild.txt
MachOObjectFile.cpp	[Object] keep trailing '\0' out of StringRef when parsing mach-o bindings	2014-09-17 01:51:43 +00:00
MachOUniversal.cpp	unique_ptrify MachOUniversalBinary::create	2014-09-03 17:41:05 +00:00
Makefile
Object.cpp	Restore the ability to check if LLVMCreateObjectFile was successful	2014-09-05 21:22:09 +00:00
ObjectFile.cpp	Don't own the buffer in object::Binary.	2014-08-19 18:44:46 +00:00
RecordStreamer.cpp
RecordStreamer.h
SymbolicFile.cpp	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00