llvm-svn: 134112

that dominates the given Use.

llvm-svn: 134111

llvm-svn: 134110

llvm-svn: 134109

This commit adds a new top subcommand "summary" to command type named "type". Currently this command
implements three commands:

type summary add <format> <typename1> [<typename2> ...]
type summary delete <typename1> [<typename2> ...]
type summary list [<typename1> [<typename2>] ...]
type summary clear

This allows you to specify the default format that will be used to display
summaries for variables, shown when you use "frame variable" or "expression", or the SBValue classes.

Examples:
type summary add "x = ${var.x}" Point

type summary list

type summary add --one-liner SimpleType

llvm-svn: 134108

llvm-svn: 134107

already makes the assumption, which is correct on ARM, that a type's alignment is
less than its alloc size. This improves codegen with Clang (which inserts a lot of
extraneous alignment specifiers) and fixes <rdar://problem/9695089>.

llvm-svn: 134106

Previously macro expanded tokens were added to Preprocessor's bump allocator and never released,
even after the TokenLexer that were lexing them was finished, thus they were wasting memory.
A very "useful" boost library was causing clang to eat 1 GB just for the expanded macro tokens.

Introduce a special cache that works like a stack; a TokenLexer can add the macro expanded tokens
in the cache, and when it finishes, the tokens are removed from the end of the cache.

Now consumed memory by expanded tokens for that library is ~ 1.5 MB.

Part of rdar://9327049.

llvm-svn: 134105

[libclang] Introduce cxcursor::getCursorParentDecl(CXCursor Cursor) and use it at the appropriate place in CIndex.cpp
No functionality change.

llvm-svn: 134104

llvm-svn: 134103

level in the public API. 

Also modified the ValueObject values to be able to display global variables
without having a valid running process. The globals will read themselves from
the object file section data if there is no process, and from the process if
there is one.

Also fixed an issue where modifications for dynamic types could cause child
values of ValueObjects to not show up if the value was unable to evaluate
itself (children of NULL pointer objects).

llvm-svn: 134102

They've been pseudos for a while now, so the decoder will never see
them in the first place.

llvm-svn: 134101

llvm-svn: 134100

initialized via initializer lists. Fixes <rdar://problem/9694686>.

llvm-svn: 134099

llvm-svn: 134098

replace the existing declaration appropriately. Patch by Jordy Rose,
fixes PR10013 / <rdar://problem/9584157>.

llvm-svn: 134097

Fixed crashes for SBValue fuzz calls.
And change 'bool SBType::IsPointerType(void)' to
'bool SBType::IsAPointerType(void)' to avoid name collision with the static 'bool SBType::IsPointerType(void *)'
function, which SWIG cannot handle.

llvm-svn: 134096

Part of rdar://9643582

llvm-svn: 134095

llvm-svn: 134094

llvm-svn: 134093

The tSpill and tRestore instructions are just copies of the tSTRspi and
tLDRspi instructions, respectively. Just use those directly instead.

llvm-svn: 134092

accessibility of an initializer which is a compound 
statement. // rdar://9694706

llvm-svn: 134091

looking up what we needed by address, which is much faster.

llvm-svn: 134090

llvm-svn: 134089

getRegForInlineAsmConstraint.

Part of rdar://9643582

llvm-svn: 134088

llvm-svn: 134087

creating a few specific register classes.

Part of rdar://9643582

llvm-svn: 134086

for the port.

Part of rdar://9643582

llvm-svn: 134085

Part of rdar://9643582

llvm-svn: 134084

Part of rdar://9643582

llvm-svn: 134083

replacing -freset-local-blocks. // rdar://9227352

llvm-svn: 134082

changes that caused all SBValue objects to completely ignore the target
lock due to bad C++ scoping of the target Mutex::Locker variables.

llvm-svn: 134081

getRegForInlineAsmConstraint.

Part of rdar://9643582

llvm-svn: 134080

via vectors.

Part of rdar://9643582

llvm-svn: 134079

llvm-svn: 134078

llvm-svn: 134072

lifetime intrinsics" due to buildbot failures.

llvm-svn: 134071

llvm-svn: 134070

For example, ".byte 256" would previously assert() when emitting an object
file. Now it generates a diagnostic that the literal value is out of range.

rdar://9686950

llvm-svn: 134069

llvm-svn: 134068