summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-vtabledump
Commit message (Collapse)AuthorAgeFilesLines
* llvm-cxxdump: Rename llvm-vtabledump to llvm-cxxdumpDavid Majnemer2015-03-157-724/+0
| | | | | | | llvm-vtabledump has grown enough functionality not related to vtables that it deserves a name which is more descriptive. llvm-svn: 232301
* Make helper functions static.Benjamin Kramer2015-03-091-1/+1
| | | | | | Found by -Wmissing-prototypes. NFC. llvm-svn: 231664
* llvm-vtabledump: Update field with a better nameDavid Majnemer2015-02-271-3/+3
| | | | llvm-svn: 230804
* llvm-vtabledump: Dump catch/throw exception structures for MS ABIDavid Majnemer2015-02-271-2/+107
| | | | llvm-svn: 230713
* llvm-vtabledump: Handle Itanium VTablesDavid Majnemer2014-11-031-47/+166
| | | | | | Add support in the vtable dumper for the Itanium ABI. llvm-svn: 221133
* Remove bogus std::error_code returns form SectionRef.Rafael Espindola2014-10-081-3/+2
| | | | | | | | | | | | | | There are two methods in SectionRef that can fail: * getName: The index into the string table can be invalid. * getContents: The section might point to invalid contents. Every other method will always succeed and returning and std::error_code just complicates the code. For example, a section can have an invalid alignment, but if we are able to get to the section structure at all and create a SectionRef, we will always be able to read that invalid alignment. llvm-svn: 219314
* llvm-vtabledump: Further simplificationDavid Majnemer2014-09-261-43/+15
| | | | | | | Hoist out calls to getSection and getContents. No functional change intended. llvm-svn: 218550
* llvm-vtabledump: Small cleanupDavid Majnemer2014-09-261-24/+24
| | | | llvm-svn: 218505
* llvm-vtabledump: strip trailing NUL bytesDavid Majnemer2014-09-261-1/+3
| | | | llvm-svn: 218502
* llvm-vtabledump: Dump RTTI structures for the MS ABIDavid Majnemer2014-09-261-15/+186
| | | | llvm-svn: 218498
* Object: Add range iterators for Archive childrenDavid Majnemer2014-09-251-4/+2
| | | | | | No functional change intended. llvm-svn: 218471
* Don't own the buffer in object::Binary.Rafael Espindola2014-08-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Canonicalize header guards into a common format.Benjamin Kramer2014-08-132-4/+4
| | | | | | | | | | Add header guards to files that were missing guards. Remove #endif comments as they don't seem common in LLVM (we can easily add them back if we decide they're useful) Changes made by clang-tidy with minor tweaks. llvm-svn: 215558
* Remove some calls to std::move.Rafael Espindola2014-08-011-3/+3
| | | | | | | | | Instead of moving out the data in a ErrorOr<std::unique_ptr<Foo>>, get a reference to it. Thanks to David Blaikie for the suggestion. llvm-svn: 214516
* Use std::unique_ptr to make the ownership explicit.Rafael Espindola2014-07-311-2/+2
| | | | llvm-svn: 214377
* llvm-vtabledump: use a std::map instead of a StringMap for VBTablesDavid Majnemer2014-07-251-6/+6
| | | | | | | | StringMap doesn't guarantee any particular iteration order, this is suboptimal when comparing llvm-vtabledump's output for two object files. llvm-svn: 213921
* llvm-vtabledump: A vtable dumperDavid Majnemer2014-07-247-0/+358
This tool's job is to dump the vtables inside object files. It is currently limited to MS ABI vf- and vb-tables but it will eventually support Itanium-style v-tables as well. Differential Revision: http://reviews.llvm.org/D4584 llvm-svn: 213903
OpenPOWER on IntegriCloud