- Mar 26, 2011
-
-
Howard Hinnant authored
llvm-svn: 128350
-
Howard Hinnant authored
llvm-svn: 128349
-
Fariborz Jahanian authored
from an objective-c message: // rdar://9005189 llvm-svn: 128348
-
Greg Clayton authored
an architecture into ArchSpec: uint32_t ArchSpec::GetMinimumOpcodeByteSize() const; uint32_t ArchSpec::GetMaximumOpcodeByteSize() const; Added an AddressClass to the Instruction class in Disassembler.h. This allows decoded instructions to know know if they are code, code with alternate ISA (thumb), or even data which can be mixed into code. The instruction does have an address, but it is a good idea to cache this value so we don't have to look it up more than once. Fixed an issue in Opcode::SetOpcodeBytes() where the length wasn't getting set. Changed: bool SymbolContextList::AppendIfUnique (const SymbolContext& sc); To: bool SymbolContextList::AppendIfUnique (const SymbolContext& sc, bool merge_symbol_into_function); This function was typically being used when looking up functions and symbols. Now if you lookup a function, then find the symbol, they can be merged into the same symbol context and not cause multiple symbol contexts to appear in a symbol context list that describes the same function. Fixed the SymbolContext not equal operator which was causing mixed mode disassembly to not work ("disassembler --mixed --name main"). Modified the disassembler classes to know about the fact we know, for a given architecture, what the min and max opcode byte sizes are. The InstructionList class was modified to return the max opcode byte size for all of the instructions in its list. These two fixes means when disassemble a list of instructions and dump them and show the opcode bytes, we can format the output more intelligently when showing opcode bytes. This affects any architectures that have varying opcode byte sizes (x86_64 and i386). Knowing the max opcode byte size also helps us to be able to disassemble N instructions without having to re-read data if we didn't read enough bytes. Added the ability to set the architecture for the disassemble command. This means you can easily cross disassemble data for any supported architecture. I also added the ability to specify "thumb" as an architecture so that we can force disassembly into thumb mode when needed. In GDB this was done using a hack of specifying an odd address when disassembling. I don't want to repeat this hack in LLDB, so the auto detection between ARM and thumb is failing, just specify thumb when disassembling: (lldb) disassemble --arch thumb --name main You can also have data in say an x86_64 file executable and disassemble data as any other supported architecture: % lldb a.out Current executable set to 'a.out' (x86_64). (lldb) b main (lldb) run (lldb) disassemble --arch thumb --count 2 --start-address 0x0000000100001080 --bytes 0x100001080: 0xb580 push {r7, lr} 0x100001082: 0xaf00 add r7, sp, #0 Fixed Target::ReadMemory(...) to be able to deal with Address argument object that isn't section offset. When an address object was supplied that was out on the heap or stack, target read memory would fail. Disassembly uses Target::ReadMemory(...), and the example above where we disassembler thumb opcodes in an x86 binary was failing do to this bug. llvm-svn: 128347
-
-
rdar://8366474Chris Lattner authored
fix the second part of rdar://8366474 - clang fails to parse ObjC selectors with '::', when :: isn't the first part of the selector. llvm-svn: 128344
-
Fariborz Jahanian authored
llvm-svn: 128343
-
Benjamin Kramer authored
It couldn't be used outside of the file because SDISelAsmOperandInfo is local to SelectionDAGBuilder.cpp. Making it a static function avoids a weird linkage dance. llvm-svn: 128342
-
Oscar Fuentes authored
Tested that MinGW/MSYS builds fine without that. llvm-svn: 128341
-
Anders Carlsson authored
llvm-svn: 128340
-
Benjamin Kramer authored
llvm-svn: 128339
-
Benjamin Kramer authored
llvm-svn: 128338
-
Douglas Gregor authored
llvm-svn: 128337
-
Douglas Gregor authored
platform implies default visibility. To achieve these, refactor our lookup of explicit visibility so that we search for both an explicit VisibilityAttr and an appropriate AvailabilityAttr, favoring the VisibilityAttr if it is present. llvm-svn: 128336
-
David Chisnall authored
Reformatted doc comments so that they are now difficult to edit in any editor that doesn't have explicit doxygen support, as per LLVM style guidelines. llvm-svn: 128335
-
Douglas Gregor authored
llvm-svn: 128334
-
Bill Wendling authored
llvm-svn: 128333
-
Bill Wendling authored
There are two ways that a later store can comletely overlap a previous store: 1. They both start at the same offset, but the earlier store's size is <= the later's size, or 2. The earlier store's offset is > the later's offset, but it's offset + size doesn't extend past the later's offset + size. llvm-svn: 128332
-
Cameron Zwarich authored
llvm-svn: 128331
-
Douglas Gregor authored
llvm-svn: 128330
-
Douglas Gregor authored
'unavailable' argument, which specifies that the declaration to which the attribute appertains is unavailable on that platform. llvm-svn: 128329
-
John McCall authored
without a warning. llvm-svn: 128328
-
Jakob Stoklund Olesen authored
Correctly terminate the range of register DBG_VALUEs when the register is clobbered or when the basic block ends. The code is now ready to deal with variables that are sometimes in a register and sometimes on the stack. We just need to teach emitDebugLoc to say 'stack slot'. llvm-svn: 128327
-
John McCall authored
usually useless, but not always. llvm-svn: 128326
-
John McCall authored
the following '@'. Conceivably, we could skip tokens until something that can validly start an @interface declaration here, but it's not clear that it matters. llvm-svn: 128325
-
John McCall authored
llvm-svn: 128324
-
Ken Dyck authored
FinalOverriders::ComputeBaseOffsets() to CharUnits. No change in functionality intended. llvm-svn: 128323
-
Johnny Chen authored
llvm-svn: 128322
-
Ken Dyck authored
intended. llvm-svn: 128321
-
Eric Christopher authored
masks to match inversely for the code as is to work. For the example given we actually want: bfi r0, r2, #1, #1 not #0, however, given the way the pattern is written it's not possible at the moment. Fixes rdar://9177502 llvm-svn: 128320
-
Bill Wendling authored
completely overlaps a previous store, thus mistakenly deleting that store. Check for this condition. llvm-svn: 128319
-
Ken Dyck authored
functionality intended. llvm-svn: 128318
-
Ken Dyck authored
functionality intended. llvm-svn: 128317
-
Sean Callanan authored
in stability fixes for the ARM and Thumb disassemblers. llvm-svn: 128316
-
Ken Dyck authored
intended. llvm-svn: 128315
-
Stephen Wilson authored
llvm-svn: 128313
-
Stephen Wilson authored
llvm-svn: 128312
-
Stephen Wilson authored
llvm-svn: 128311
-
Ted Kremenek authored
llvm-svn: 128310
-
Kevin Enderby authored
llvm-svn: 128309
-