| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | llvm-objdump: deal with invalid ARM encodings slightly better. | Tim Northover | 2016-04-22 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | Before we printed a warning to stderr and left the actual output stream in a mess. This tries to print a .long or .short representation of what we saw (as if there was a data-in-code directive). This isn't guaranteed to restore synchronization in Thumb-mode (if the invalid instruction was supposed to be 32-bits, we may be off-by-16 for the rest of the function). But there's no certain way to deal with that, and it's invalid code anyway (if the data really wasn't an instruction, the user can add proper .data_in_code directives if they care) llvm-svn: 267250 | ||||
| * | Have MachOObjectFile::isValidArch() accept armv7 | Frederic Riss | 2015-06-16 | 1 | -0/+1 |
| | | | | | llvm-svn: 239833 | ||||
| * | Make llvm-objdump handle both arm and thumb disassembly from the same Mach-O | Kevin Enderby | 2014-08-18 | 1 | -0/+15 |
| file with -macho, the Mach-O specific object file parser option. After some discussion I chose to do this implementation contained in the logic of llvm-objdump’s MachODump.cpp using a second disassembler for thumb when needed and with updates mostly contained in the MachOObjectFile class. llvm-svn: 215931 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|