| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
lldb crashes with universal file containing skinny BSD archives when doing DWARF with .o file debugging.
llvm-svn: 182437
|
| |
|
|
|
|
| |
operand of a unary address-of expression, not for *all* expressions!
llvm-svn: 182436
|
| |
|
|
| |
llvm-svn: 182435
|
| |
|
|
| |
llvm-svn: 182434
|
| |
|
|
|
|
| |
function templates can use it as a return type.
llvm-svn: 182433
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*that* easy...
Try a bit harder to disambiguate. This is mostly straightforward, but for
=-style initializers, we actually need to know where an expression ends:
[foo = bar baz]
is a message send, whereas
[foo = bar + baz]
is a lambda-introducer. Handle this by parsing the expression eagerly, and
replacing it with an annotation token. By chance, we use the *exact same*
parsing rules in both cases (except that we need to assume we're inside a
message send for the parse, to turn off various forms of inapplicable
error recovery).
llvm-svn: 182432
|
| |
|
|
|
|
|
| |
a RegScavenger object on it's own.
llvm-svn: 182430
|
| |
|
|
| |
llvm-svn: 182429
|
| |
|
|
|
|
|
|
| |
exec'ing itself into a new program. This currently is only enabled for Darwin since we exec from 64 bit to 32 bit and vice versa for 'x86_64' targets.
This can easily be adapted for linux and other platforms, but I didn't want to break any buildbots by assuming it will work.
llvm-svn: 182428
|
| |
|
|
| |
llvm-svn: 182427
|
| |
|
|
|
|
|
|
| |
dive-in and out of a subexpression.
Fixes <rdar://problem/13941891>.
llvm-svn: 182426
|
| |
|
|
|
|
| |
does.
llvm-svn: 182425
|
| |
|
|
| |
llvm-svn: 182424
|
| |
|
|
|
|
|
| |
variables when they are used in such unevaluated
contexts as __typeof, etc. // rdar://13942025
llvm-svn: 182423
|
| |
|
|
| |
llvm-svn: 182422
|
| |
|
|
|
|
| |
added.
llvm-svn: 182421
|
| |
|
|
| |
llvm-svn: 182420
|
| |
|
|
|
|
|
|
| |
Solaris doesn't have an endian.h header, but SPARC is the only
big-endian architecture that runs Solaris, so just use that to detect
endianness at compile time.
llvm-svn: 182419
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libExecutionEngine. Move method implementations that aren't specific to
allocation out of SectionMemoryManager and into RTDyldMemoryManager.
This is in preparation for exposing RTDyldMemoryManager through the C
API.
This is a fixed version of r182407 and r182411. That first revision
broke builds because I forgot to move the conditional includes of
various POSIX headers from SectionMemoryManager into
RTDyldMemoryManager. Those includes are necessary because of how
getPointerToNamedFunction works around the glibc libc_nonshared.a thing.
The latter revision still broke things because I forgot to include
llvm/Config/config.h.
llvm-svn: 182418
|
| |
|
|
| |
llvm-svn: 182415
|
| |
|
|
|
|
|
|
|
|
| |
Yet another implementation of the python in dSYM autoload :)
This time we are going with a ternary setting:
true - load, do not warn
false - do not load, do not warn
warn - do not load, warn (default)
llvm-svn: 182414
|
| |
|
|
|
|
| |
SectionMemoryManager, but is now in RTDyldMemoryManager.
llvm-svn: 182412
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libExecutionEngine. Move method implementations that aren't specific to
allocation out of SectionMemoryManager and into RTDyldMemoryManager.
This is in preparation for exposing RTDyldMemoryManager through the C
API.
This is a fixed version of r182407. That revision broke builds because I
forgot to move the conditional includes of various POSIX headers from
SectionMemoryManager into RTDyldMemoryManager. Those includes are
necessary because of how getPointerToNamedFunction works around the
glibc libc_nonshared.a thing.
llvm-svn: 182411
|
| |
|
|
|
|
| |
This binary file is created from shared.c.
llvm-svn: 182410
|
| |
|
|
| |
llvm-svn: 182409
|
| |
|
|
|
|
|
|
| |
the C API to provide their own way of allocating JIT memory (both code
and data) and finalizing memory permissions (page protections, cache
flush).
llvm-svn: 182408
|
| |
|
|
|
|
|
|
|
|
| |
libExecutionEngine. Move method implementations that aren't specific to
allocation out of SectionMemoryManager and into RTDyldMemoryManager.
This is in preparation for exposing RTDyldMemoryManager through the C
API.
llvm-svn: 182407
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
common function. The C++1y contextual implicit conversion rules themselves are
not yet implemented, however.
This also fixes a subtle bug where template instantiation context notes were
dropped for diagnostics coming from conversions for integral constant
expressions -- we were implicitly slicing a SemaDiagnosticBuilder into a
DiagnosticBuilder when producing these diagnostics, and losing their context
notes in the process.
llvm-svn: 182406
|
| |
|
|
|
|
|
| |
I will try to avoid creating these std::strings, but for now this gets
the tests passing with libc++.
llvm-svn: 182405
|
| |
|
|
|
|
| |
duplicate lookup in the insertion case
llvm-svn: 182404
|
| |
|
|
|
|
|
|
| |
them from
(no intended behavior change)
llvm-svn: 182403
|
| |
|
|
|
|
| |
Found by -Wdocumentation.
llvm-svn: 182402
|
| |
|
|
| |
llvm-svn: 182401
|
| |
|
|
| |
llvm-svn: 182400
|
| |
|
|
|
|
| |
Keeps it consistent between ASan and LSan.
llvm-svn: 182399
|
| |
|
|
|
|
|
| |
A user request such as: memory read -fc -s10 -c1 *charPtrPtr would cause us to crash upon trying to read 1 char of size 10 from memory
This request is now translated into: memory read -fc -s1 -c10 *charPtrPtr (i.e. read 10 chars of size 1 from memory) which is probably also what the user originally wanted
llvm-svn: 182398
|
| |
|
|
| |
llvm-svn: 182397
|
| |
|
|
| |
llvm-svn: 182396
|
| |
|
|
| |
llvm-svn: 182395
|
| |
|
|
| |
llvm-svn: 182394
|
| |
|
|
| |
llvm-svn: 182390
|
| |
|
|
| |
llvm-svn: 182389
|
| |
|
|
|
|
|
|
|
|
| |
The intrinsic calls are dropped, but the annotated value is propagated.
Fixes PR 15253
Original patch by Zeng Bin!
llvm-svn: 182387
|
| |
|
|
| |
llvm-svn: 182386
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Although I had added some support for the BDZ/BDNZ branches into the selector
(in r158204), I had not correctly adjusted the condition at the top of the
loop. As a result, these branches were still essentially unsupported.
This fixes PR16086. Unfortunately, any test case would be very large (because
it would need to force the loop backedge to exceed the range of the 16-bit
immediate).
llvm-svn: 182385
|
| |
|
|
| |
llvm-svn: 182384
|
| |
|
|
|
|
| |
Also, define CAN_SANITIZE_LEAKS.
llvm-svn: 182383
|
| |
|
|
| |
llvm-svn: 182382
|
| |
|
|
| |
llvm-svn: 182380
|
| |
|
|
| |
llvm-svn: 182379
|