| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
http://llvm.org/bugs/show_bug.cgi?id=12924
This issue was that the source location was pointing to a
non-printable character and so CaretEnd was pointing one
_column_ past the caret but not one _character_ past the
caret. So the conversion between column and byte locations
wasn't working (because the conversion is only valid from
the first column or byte of a character).
llvm-svn: 157372
|
| |
|
|
| |
llvm-svn: 157371
|
| |
|
|
|
|
|
|
| |
volatile reference to a temporary is not viable. My interpretation is that
DR1152 was a bugfix, not a rule change for C++11, so this is not conditional on
the language mode. This matches g++'s behavior.
llvm-svn: 157370
|
| |
|
|
|
|
| |
sizeof/sizeof.
llvm-svn: 157369
|
| |
|
|
| |
llvm-svn: 157368
|
| |
|
|
|
|
| |
uint16_t. Simplify loop iterating over one of those tables. No functional change intended.
llvm-svn: 157367
|
| |
|
|
|
|
|
|
| |
builder to have an explicit
short-circuit of the Python SWIG building, rather than relying on the SDKROOT being set.
llvm-svn: 157363
|
| |
|
|
|
|
| |
Conceptually, this is part of -Wunused-value, but I added a separate flag -Wunused-volatile-lvalue so it doesn't get turned off by accident with -Wno-unused-value. I also made a few minor improvements to existing unused value warnings in the process. <rdar://problem/11516811>.
llvm-svn: 157362
|
| |
|
|
|
|
|
| |
Supports the use-case scenario of immediately continuing the process once attached.
Add a simple completion test case from "process attach --con" to "process attach --continue ".
llvm-svn: 157361
|
| |
|
|
|
|
|
|
| |
Portions of this patch by Xi Wang. Reviewed by Jordy Rose. Thank you both.
Codegen support will follow soon.
llvm-svn: 157360
|
| |
|
|
|
|
| |
statement. // rdar://11474836.
llvm-svn: 157359
|
| |
|
|
|
|
| |
intended.
llvm-svn: 157358
|
| |
|
|
| |
llvm-svn: 157357
|
| |
|
|
|
|
| |
rdar://11357807
llvm-svn: 157356
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Live ranges with a constrained register class may benefit from splitting
around individual uses. It allows the remaining live range to use a
larger register class where it may allocate. This is like spilling to a
different register class.
This is only attempted on constrained register classes.
<rdar://problem/11438902>
llvm-svn: 157354
|
| |
|
|
|
|
|
|
| |
through the Python scripting bridge.
Add/modify some test cases.
llvm-svn: 157353
|
| |
|
|
|
|
| |
incompatible to -fms-compatibility.
llvm-svn: 157352
|
| |
|
|
|
|
| |
in JSON.
llvm-svn: 157351
|
| |
|
|
|
|
|
|
| |
used here.
It fixes test/Tooling on Win32 hosts.
llvm-svn: 157350
|
| |
|
|
| |
llvm-svn: 157349
|
| |
|
|
| |
llvm-svn: 157348
|
| |
|
|
|
|
|
|
|
|
|
| |
idiom that is used commonly in setters:
[backingValue autorelease];
backingValue = [newValue retain]; // in general a +1 assign
rdar://9914061
llvm-svn: 157347
|
| |
|
|
|
|
| |
rdar://11518308
llvm-svn: 157346
|
| |
|
|
|
|
|
|
|
| |
to the "watchpoint list" command.
Add default Process::GetWatchpointSupportInfo() impl which returns an error of "not supported".
Add "qWatchpointSupportInfo" packet to the gdb communication layer to support this, and modify TestWatchpointCommands.py to test it.
llvm-svn: 157345
|
| |
|
|
| |
llvm-svn: 157342
|
| |
|
|
|
|
|
|
| |
CHECK. The latter error was hidden by the former, and the test harness
used by e.g. "make check" silently ignored that opt was printing an
error message about an unknown flag instead of running on the test file.
llvm-svn: 157341
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the coalescer keeps live intervals and machine code in sync at
all times, it needs to deal with identity copies differently.
When merging two virtual registers, all identity copies are removed
right away. This means that other identity copies must come from
somewhere else, and they are going to have a value number.
Deal with such copies by merging the value numbers before erasing the
copy instruction. Otherwise, we leave dangling value numbers in the live
interval.
This fixes PR12927.
llvm-svn: 157340
|
| |
|
|
| |
llvm-svn: 157339
|
| |
|
|
| |
llvm-svn: 157337
|
| |
|
|
|
|
| |
Patch by Jush Lu <jush.msn@gmail.com>.
llvm-svn: 157336
|
| |
|
|
|
|
| |
that allows easy refactoring across translation units.
llvm-svn: 157331
|
| |
|
|
| |
llvm-svn: 157330
|
| |
|
|
| |
llvm-svn: 157329
|
| |
|
|
| |
llvm-svn: 157328
|
| |
|
|
|
|
|
|
| |
race conditions where we are in the middle of trying to service an event when we go to Destroy.
The AttachCompletionHandler should note that it has restarted the target if it indeed does so.
llvm-svn: 157327
|
| |
|
|
| |
llvm-svn: 157326
|
| |
|
|
|
|
| |
Apparently LLVM only stopped emitting this after LLVM 3.0
llvm-svn: 157325
|
| |
|
|
|
|
|
|
| |
inline threshold if the global inline threshold is lower (as for -Oz).
Reviewed by Chandler Carruth and Bill Wendling.
llvm-svn: 157323
|
| |
|
|
| |
llvm-svn: 157320
|
| |
|
|
| |
llvm-svn: 157319
|
| |
|
|
| |
llvm-svn: 157318
|
| |
|
|
| |
llvm-svn: 157317
|
| |
|
|
| |
llvm-svn: 157315
|
| |
|
|
| |
llvm-svn: 157314
|
| |
|
|
| |
llvm-svn: 157313
|
| |
|
|
|
|
| |
case.
llvm-svn: 157312
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
start with a cv-qualifier. DeclaratorDecl::getTypeSpecStartLoc() does not
produce the location of the first type-specifier (the cv-qualifier) in this
case, because we don't track source locations for cv-qualifiers.
No test here: I've not found a way to test this with a lit-style test, and
introducing a gtest test for this seems unwarranted. Suggestions welcome!
Patch by Daniel Jasper!
llvm-svn: 157311
|
| |
|
|
|
|
|
|
| |
pointer, but such folding encounters side-effects, ignore the side-effects
rather than performing them at runtime: CodeGen generates wrong code for
__builtin_object_size in that case.
llvm-svn: 157310
|
| |
|
|
| |
llvm-svn: 157309
|
| |
|
|
| |
llvm-svn: 157308
|