Bjorn Steinbrink ea388503c4 Restore the ability to check if LLVMCreateObjectFile was successful ... Summary: Until r216870 LLVMCreateObjectFile returned nullptr in case of an error, so callers could check if the call was successful. Now, it always returns an OwningBinary wrapped as an LLVMObjectFileRef, so callers can't check if the call was successul. This results in a segfault running e.g. llvm-c-test --object-list-sections < /dev/null So the old behaviour should be restored. Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D5143 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217279 91177308-0d34-0410-b5e6-96231b3b80d8		2014-09-05 21:22:09 +00:00
..
Archive.cpp
Binary.cpp
CMakeLists.txt
COFFObjectFile.cpp
COFFYAML.cpp
ELF.cpp
ELFObjectFile.cpp
ELFYAML.cpp
Error.cpp
IRObjectFile.cpp	unique_ptrify IRObjectFile::createIRObjectFile	2014-09-03 17:59:23 +00:00
LLVMBuild.txt
MachOObjectFile.cpp	Adds the next bit of support for llvm-objdump’s -private-headers for executable Mach-O files.	2014-09-04 16:54:47 +00:00
MachOUniversal.cpp
Makefile
Object.cpp	Restore the ability to check if LLVMCreateObjectFile was successful	2014-09-05 21:22:09 +00:00
ObjectFile.cpp
RecordStreamer.cpp
RecordStreamer.h
SymbolicFile.cpp	unique_ptrify IRObjectFile::createIRObjectFile	2014-09-03 17:59:23 +00:00