bcm5719-llvm/llvm/tools/macho-dump, branch meklort-10.0.1

Remove macho-dump. Its functionality is now covered by llvm-readobj.

2015-09-22T17:46:10+00:00

Approved by: Rafael Espindola, Eric Christopher, Jim Grosbach, Alex Rosenberg llvm-svn: 248302

[Object, MachO] Introduce MachOObjectFile::load_commands() range iterator.

2015-06-03T22:19:36+00:00

Summary: Now users don't have to manually deal with getFirstLoadCommandInfo() / getNextLoadCommandInfo(), calculate the number of load segments, etc. No functionality change. Test Plan: regression test suite Reviewers: rafael, lhames, loladiro Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D10144 llvm-svn: 238983

Add printing the LC_LINKER_OPTION load command with llvm-objdump’s -private-headers.

2014-12-18T00:53:40+00:00

Also corrected the name of the load command to not end in an ’S’ as well as corrected the name of the MachO::linker_option_command struct and other places that had the word option as plural which did not match the Mac OS X headers. llvm-svn: 224485

Adds the next bit of support for llvm-objdump’s -private-headers for executable Mach-O files.

2014-09-04T16:54:47+00:00

This adds the printing of more load commands, so that the normal load commands in a typical X86 Mach-O executable can all be printed. llvm-svn: 217172

Don't own the buffer in object::Binary.

2014-08-19T18:44:46+00:00

Owning the buffer is somewhat inflexible. Some Binaries have sub Binaries (like Archive) and we had to create dummy buffers just to handle that. It is also a bad fit for IRObjectFile where the Module wants to own the buffer too. Keeping this ownership would make supporting IR inside native objects particularly painful. This patch focuses in lib/Object. If something elsewhere used to own an Binary, now it also owns a MemoryBuffer. This patch introduces a few new types. * MemoryBufferRef. This is just a pair of StringRefs for the data and name. This is to MemoryBuffer as StringRef is to std::string. * OwningBinary. A combination of Binary and a MemoryBuffer. This is needed for convenience functions that take a filename and return both the buffer and the Binary using that buffer. The C api now uses OwningBinary to avoid any change in semantics. I will start a new thread to see if we want to change it and how. llvm-svn: 216002

Remove some calls to std::move.

2014-08-01T14:31:55+00:00

Instead of moving out the data in a ErrorOr>, get a reference to it. Thanks to David Blaikie for the suggestion. llvm-svn: 214516

Use std::unique_ptr to make the ownership explicit.

2014-07-31T03:12:45+00:00

llvm-svn: 214377

macho-dump: add code to print LC_ID_DYLIB load commands.

2014-06-30T14:40:57+00:00

I want to check them in lld. llvm-svn: 212043

Remove 'using std::error_code' from tools.

2014-06-13T03:07:50+00:00

llvm-svn: 210876

Don't use 'using std::error_code' in include/llvm.

2014-06-12T21:46:39+00:00

This should make sure that most new uses use the std prefix. llvm-svn: 210835