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
..
Analysis
Assembler
Bindings
Bitcode
BugPoint
CodeGen	[ARM] Do not perform a tail call when the caller returns several values.	2014-09-18 21:17:50 +00:00
DebugInfo
ExecutionEngine
Feature
FileCheck
Instrumentation
Integer
JitListener
Linker
LTO	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
MC	ARM: prevent crash on ELF directives on COFF	2014-09-18 04:28:29 +00:00
Object
Other
TableGen	[TableGen] Fully resolve class-instance values before defs in multiclasses	2014-09-16 17:14:13 +00:00
tools	LTO: introduce object file-based on-disk module format.	2014-09-18 21:28:49 +00:00
Transforms	[IndVarSimplify] Partially revert r217953 to see if this fixes the bots.	2014-09-17 16:35:09 +00:00
Unit
Verifier
YAMLParser
.clang-format
CMakeLists.txt
lit.cfg	Exclude known and bugzilled failures from UBSan bootstrap	2014-09-17 20:17:52 +00:00
lit.site.cfg.in
Makefile
Makefile.tests
TestRunner.sh