| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
delegating to TestBase.runCmd()
to execute the debugger command. This will result in a more semantic assert message than just the
command failed message like before:
AssertionError: False is not True : Command 'thread list' returns successfully
And now, we will have:
AssertionError: False is not True : Process state is stopped due to breakpoint
llvm-svn: 117569
|
| |
|
|
|
|
|
|
| |
logging for type importing, making errors much
easier to diagnose. Also removed some Objective-C
related logging.
llvm-svn: 117568
|
| |
|
|
|
|
| |
Part 2 of rdar://problem/8595231
llvm-svn: 117567
|
| |
|
|
| |
llvm-svn: 117563
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
purpose is clear
the breakpoint associated with the (filename, line_number) combo when an arrow is pointing to
a source position using Emacs Grand Unified Debugger library to interact with lldb.
The current implmentation is insufficient in that it only asks the breakpoint whether it is
associated with a breakpoint resolver with FileLine type and whether it matches the (filename, line_number)
combo. There are other breakpoint resolver types whose breakpoint locations can potentially
match the (filename, line_number) combo.
The BreakpointResolver, BreakpointResolverName, BreakpointResolverAddress, and BreakpointResolverFileLine
classes have extra static classof methods to support LLVM style type inquiry through isa, cast, and dyn_cast.
The Breakpoint class has an API method bool GetMatchingFileLine(...) which is invoked from CommandObjectBreak.cpp
to implement the "breakpoint clear" command.
llvm-svn: 117562
|
| |
|
|
| |
llvm-svn: 117561
|
| |
|
|
| |
llvm-svn: 117560
|
| |
|
|
| |
llvm-svn: 117559
|
| |
|
|
|
|
| |
Also do some minor refactoring to reduce indentation.
llvm-svn: 117558
|
| |
|
|
|
|
| |
Pointed out by Chris!
llvm-svn: 117557
|
| |
|
|
|
|
|
|
|
|
| |
http://llvm.org/bugs/show_bug.cgi?id=8493
File name "2010-10-19-14:10:49.059609" is non-portable.
Do not use ':' in the pathname as it is not permitted on windows platforms.
llvm-svn: 117556
|
| |
|
|
|
|
| |
to set a breakpoint.
llvm-svn: 117555
|
| |
|
|
|
|
| |
"2010-10-19-14:10:49.059609" is non-portable.
llvm-svn: 117554
|
| |
|
|
| |
llvm-svn: 117553
|
| |
|
|
| |
llvm-svn: 117552
|
| |
|
|
|
|
| |
a null pointer.
llvm-svn: 117551
|
| |
|
|
|
|
|
|
| |
timers to be dumped whenever the ASTUnit is destroyed. Instead, just
print the time elapsed for each operation after we perform the
operation.
llvm-svn: 117550
|
| |
|
|
| |
llvm-svn: 117548
|
| |
|
|
| |
llvm-svn: 117547
|
| |
|
|
| |
llvm-svn: 117546
|
| |
|
|
|
|
| |
UnitTests for building all the unit tests.
llvm-svn: 117545
|
| |
|
|
| |
llvm-svn: 117544
|
| |
|
|
| |
llvm-svn: 117543
|
| |
|
|
| |
llvm-svn: 117541
|
| |
|
|
|
|
| |
global, make them local to a decl.
llvm-svn: 117540
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the scope checker. With that done, turn an indirect goto into a
protected scope into a hard error; otherwise IR generation has to start
worrying about declarations not dominating their scopes, as exemplified
in PR8473.
If this really affects anyone, I can probably adjust this to only hard-error
on possible indirect gotos into VLA scopes rather than arbitrary scopes.
But we'll see how people cope with the aggressive change on the marginal
feature.
llvm-svn: 117539
|
| |
|
|
| |
llvm-svn: 117538
|
| |
|
|
|
|
|
|
| |
location before the
first one if the redeclaration comes from a friend decl.
llvm-svn: 117537
|
| |
|
|
|
|
|
|
| |
DeclContext,
meaning we need to rewrite its name lookup table in a chained PCH.
llvm-svn: 117536
|
| |
|
|
| |
llvm-svn: 117535
|
| |
|
|
| |
llvm-svn: 117534
|
| |
|
|
|
|
| |
chained PCH.
llvm-svn: 117533
|
| |
|
|
|
|
| |
and it's too much trouble to push for. Fixes PR8478.
llvm-svn: 117532
|
| |
|
|
| |
llvm-svn: 117531
|
| |
|
|
|
|
|
| |
I'll work with Jim, Owen, and Bill on an alternative testing strategy until
the assembly parser is available.
llvm-svn: 117530
|
| |
|
|
|
|
| |
of nearbyintf on MSVC. [PR8466]
llvm-svn: 117529
|
| |
|
|
|
|
|
|
| |
Thanks to Yuri Gribov and Vladimir Kirillov!
*BSD(s) have environ(7) in CRT startup and cannot resolve "environ" at linking llvm.so.
environ(7) is used inlib/System/Unix/Program.inc.
llvm-svn: 117528
|
| |
|
|
|
|
|
|
| |
attribute.
Part of rdar://problem/8595231
llvm-svn: 117526
|
| |
|
|
| |
llvm-svn: 117525
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
is that we need more information to decide the exact conditions for whether
one ObjCObjectPointer is an acceptable return/parameter override for another,
so we're going to disable that entire class of warning for now. The
"forward developement" warning category, -Wmethod-signatures, can receive
unrestricted feature work, and when we're happy with how it acts, we'll
turn it on by default.
This is a pretty conservative change, and nobody's totally content with it.
llvm-svn: 117524
|
| |
|
|
|
|
|
| |
doesn't mean that you can't get a .o file. Apparently
this is confusing :)
llvm-svn: 117523
|
| |
|
|
| |
llvm-svn: 117522
|
| |
|
|
|
|
| |
<rdar://problem/8481311>.
llvm-svn: 117521
|
| |
|
|
|
|
| |
to fail. Ugh.
llvm-svn: 117520
|
| |
|
|
|
|
|
|
|
|
| |
- For now, loads of [r, r] addressing mode is the same as the
[r, r lsl/lsr/asr #] variants. ARMBaseInstrInfo::getOperandLatency() should
identify the former case and reduce the output latency by 1.
- Also identify [r, r << 2] case. This special form of shifter addressing mode
is "free".
llvm-svn: 117519
|
| |
|
|
|
|
| |
by the number of defs first for it to match the instruction itinerary.
llvm-svn: 117518
|
| |
|
|
| |
llvm-svn: 117517
|
| |
|
|
|
|
|
|
| |
variables by name. It was accidentally getting all the globals
for the compile unit that contained the global variable named
NAME.
llvm-svn: 117516
|
| |
|
|
| |
llvm-svn: 117515
|
| |
|
|
|
|
|
| |
Bruno, please review, but I'm pretty sure this is right.
Patch by Alex Mac!
llvm-svn: 117514
|