- Aug 23, 2012
-
-
Eric Christopher authored
llvm-svn: 162421
-
Andrew Trick authored
The logic for recomputing latency based on a ScheduleDAG edge was shady. This bypasses the problem by requiring the client to provide operand indices. This ensures consistent use of the machine model's API. llvm-svn: 162420
-
Johnny Chen authored
Make it so that "b 245" should set a breakpoint at line 245 of the current file. Also add a simple test file. llvm-svn: 162419
-
rdar://problem/12022079Greg Clayton authored
Added a new "interpreter" properties to encapsulate any properties for the command interpreter. Right now this contains only "expand-regex-aliases", so you can now enable (disabled by default) the echoing of the command that a regular expression alias expands to: (lldb) b main Breakpoint created: 1: name = 'main', locations = 1 Note that the expanded regular expression command wasn't shown by default. You can enable it if you want to: (lldb) settings set interpreter.expand-regex-aliases true (lldb) b main breakpoint set --name 'main' Breakpoint created: 1: name = 'main', locations = 1 Also enabled auto completion for enumeration option values (OptionValueEnumeration) and for boolean option values (OptionValueBoolean). Fixed auto completion for settings names when nothing has been type (it should show all settings). llvm-svn: 162418
-
Akira Hatanaka authored
the temporary register that was used to load the immediate. Currently, it always returns register $at, but this will change if, in the future, we decide to use another register. No changes in functionality. llvm-svn: 162417
-
Chad Rosier authored
llvm-svn: 162416
-
Akira Hatanaka authored
Mips16RegisterInfo/MipsSERegisterInfo. No changes in functionality. llvm-svn: 162413
-
Ted Kremenek authored
llvm-svn: 162412
-
Ted Kremenek authored
llvm-svn: 162411
-
Chad Rosier authored
requires codegen support. llvm-svn: 162410
-
Jakob Stoklund Olesen authored
When reporting an error for a defm, we would previously only report the location of the outer defm, which is not always where the error is. Now we also print the location of the expanded multiclass defs: lib/Target/X86/X86InstrSSE.td:2902:12: error: foo defm ADD : basic_sse12_fp_binop_s<0x58, "add", fadd, SSE_ALU_ITINS_S>, ^ lib/Target/X86/X86InstrSSE.td:2801:11: note: instantiated from multiclass defm PD : sse12_fp_packed<opc, !strconcat(OpcodeStr, "pd"), OpNode, VR128, ^ lib/Target/X86/X86InstrSSE.td:194:5: note: instantiated from multiclass def rm : PI<opc, MRMSrcMem, (outs RC:$dst), (ins RC:$src1, x86memop:$src2), ^ llvm-svn: 162409
-
Argyrios Kyrtzidis authored
a deterministic order, to avoid random test failures. llvm-svn: 162408
-
Dmitri Gribenko authored
name. This should reduce the amount of warning false positives about bad HTML in comments when the comment author intended to put a reference to a template. This change will also enable us parse the comment as intended in these cases. Fixes part 1 of PR13374. llvm-svn: 162407
-
Jim Ingham authored
llvm-svn: 162406
-
Anna Zaks authored
llvm-svn: 162405
-
Jim Grosbach authored
The MCInst is immediately passed to the copy-constructor for local storage, so there's no need for the parameter itself to be by-value. llvm-svn: 162404
-
Chad Rosier authored
No functional change intended. llvm-svn: 162403
-
Daniel Dunbar authored
llvm-svn: 162402
-
- Aug 22, 2012
-
-
Jim Ingham authored
Rework how the API mutex is acquired when filling out an ExecutionContext from an ExecutionContextRef, particularly in the SBThread & SBFrame interfaces. Instead of filling the whole context & then getting the API mutex, we now get only the target, acquire the API mutex from it, then fill out the rest of the context. This removes a race condition where you get a ThreadSP, then wait on the API mutex while another command Destroy's the Thread you've just gotten. Also fixed the ExecutionContextRef::Get*SP calls so they don't return invalid objects. Also fixed the ExecutionContext::Has*Scope calls so they don't claim to have a scope if the object representing that scope has been destroyed. Also fixed a think-o in Thread::IsValid which was causing it to return the opposite of the desired value. <rdar://problem/11995490> llvm-svn: 162401
-
Jim Ingham authored
llvm-svn: 162400
-
Anna Zaks authored
llvm-svn: 162399
-
Anna Zaks authored
The checker adds assumptions that the return values from the known APIs are non-nil. Teach the checker about NSArray/NSMutableArray/NSOrderedSet objectAtIndex, objectAtIndexedSubscript. llvm-svn: 162398
-
Jason Molenda authored
Change the man page install phase to only run in "desktop" and "desktop-no-xpc" targets, not for the "ios" target. llvm-svn: 162397
-
Chad Rosier authored
llvm-svn: 162396
-
Chad Rosier authored
llvm-svn: 162394
-
Chad Rosier authored
llvm-svn: 162393
-
Chad Rosier authored
llvm-svn: 162392
-
Alexander Kornienko authored
static variables. llvm-svn: 162391
-
Chad Rosier authored
Eventually, we'll need a way of mapping tokens (and their IdentifierInfo*) to the operands computed by buildMSAsmPieces(). llvm-svn: 162388
-
Johnny Chen authored
Modified .lldb-loggings now to direct the lldb log files to the same session directory which also houses the test logs. llvm-svn: 162387
-
Ted Kremenek authored
another way to whitelist these special cases. This is an intermediate patch. llvm-svn: 162386
-
Chad Rosier authored
llvm-svn: 162385
-
Ted Kremenek authored
As part of this change, I discovered that a few of our tests were not testing the RangeConstraintManager. Luckily all of those passed when I moved them over to use that constraint manager. llvm-svn: 162384
-
Benjamin Kramer authored
llvm-svn: 162383
-
Chad Rosier authored
The parser still can't handle all cases, so fall back to emitting a simple MSAsmStmt if we get into trouble. llvm-svn: 162382
-
Chad Rosier authored
Assertion failed: (Start.isValid() == End.isValid() && "Start and end should either both be valid or both be invalid!") when parsing inline asm. SMLoc assumes that the first char * in the source is invalid. However, when parsing an inline asm the mnemonic is at this location. I don't want to change SMLoc, so use a trivial workaround. llvm-svn: 162381
-
Benjamin Kramer authored
The conditions described by POSIX can never happen with IEEE-754 floats. When the function is const we can emit a single sse4.1 instruction for it, without losing anything :) llvm-svn: 162379
-
Johnny Chen authored
Demonstrate how to use the config file and the pre-flight functionality to route the lldb gdb-remote log messages into individually named log destinations. In the simple usage-lldb-loggings example, we ran two cases which resulted in two lldb_log files. llvm-svn: 162378
-
Greg Clayton authored
llvm-svn: 162376
-
Benjamin Kramer authored
There were missed optimizations when the system headers didn't have attributes in place, specifically: - Add copysign, exp2, log2, nearbyint, rint and trunc to the list. These are functions that get inlined by LLVM's optimizer, but only when they have the right attributes. - Mark copysign, fabs, fmax, fmin and trunc const unconditionally. Previously these were only const with -fno-math-errno, but they never set errno per POSIX. For ceil/floor/nearbyint/round I'm not aware of any implementation that sets errno, but POSIX says it may signal overflow so I left them alone for now. llvm-svn: 162375
-