| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
references [-cxx-abi microsoft]
llvm-svn: 159296
|
| |
|
|
| |
llvm-svn: 159295
|
| |
|
|
| |
llvm-svn: 159294
|
| |
|
|
|
|
|
| |
property retains a block object as it could be on
the stack. // rdar://11761511
llvm-svn: 159293
|
| |
|
|
| |
llvm-svn: 159292
|
| |
|
|
|
|
| |
assertion where the mutex in the "module_list" local variable would assert when the lldb_private::Mutex would destruct. What was happening was the mutex in the module list was being locked by a local locker object and then "module_list" would get destroyed before the locker and the locker still had the mutex locked which would cause the pthread call to destroy the mutex to fail with "Resource busy" and it would cause a mutex leak.
llvm-svn: 159291
|
| |
|
|
|
|
| |
before, so we don't incorrectly think arguments of function type are non-POD.
llvm-svn: 159290
|
| |
|
|
|
|
|
|
| |
range in a block given an address. Since blocks can have multiple discontiguous ranges, it helps to be able to get the current address range for the current block in a frame. This can be used in code like:
curr_block_range = lldb.frame.block.range[lldb.frame.addr]
llvm-svn: 159289
|
| |
|
|
|
|
| |
threads in a process.
llvm-svn: 159288
|
| |
|
|
|
|
| |
returning true if the line entry is valid, not just if the opaque pointer to lldb_private::LineEntry is non NULL.
llvm-svn: 159287
|
| |
|
|
|
|
| |
allow you to dump your current process state out to a crash log file. This will dump all of the target module information with all load addresses, UUID values, and shared library paths, as well as all thread stacks and the crash log header. This will make it easy for us to save the current state of a process and then reload it later into LLDB.
llvm-svn: 159286
|
| |
|
|
|
|
| |
thread safe.
llvm-svn: 159285
|
| |
|
|
| |
llvm-svn: 159284
|
| |
|
|
| |
llvm-svn: 159283
|
| |
|
|
|
|
|
| |
when it appears to be unused and occurs in a header.
// rdar://11202617
llvm-svn: 159282
|
| |
|
|
|
|
| |
Patch by Ivan Llopard!
llvm-svn: 159281
|
| |
|
|
|
|
| |
being updated. Will fix that in a second.
llvm-svn: 159280
|
| |
|
|
| |
llvm-svn: 159279
|
| |
|
|
|
|
| |
fabricated one)
llvm-svn: 159278
|
| |
|
|
|
|
|
|
| |
overwrite the status of the result if
the python command has set it.
llvm-svn: 159273
|
| |
|
|
|
|
|
|
|
|
|
| |
Original commit message:
If a constant or a function has linkonce_odr linkage and unnamed_addr, mark it
hidden. Being linkonce_odr guarantees that it is available in every dso that
needs it. Being a constant/function with unnamed_addr guarantees that the
copies don't have to be merged.
llvm-svn: 159272
|
| |
|
|
|
|
| |
have only one semantic string value attached to it), at a cost of adding an additional token.
llvm-svn: 159270
|
| |
|
|
|
|
| |
We already have a pointer to the beginning of the token, so use it to extract the text instead.
llvm-svn: 159269
|
| |
|
|
|
|
|
|
| |
requiring a module. Original patch by Sunay Ismail, simplified by Arnaud
de Grandmaison, then complicated by me (if a triple was specified on the
command line, output help for that triple, not for the default).
llvm-svn: 159268
|
| |
|
|
| |
llvm-svn: 159267
|
| |
|
|
| |
llvm-svn: 159266
|
| |
|
|
|
|
|
|
|
|
|
| |
before the expression root. Any existing operators that are changed to use one
of them needs to be moved between it and the expression root, and recursively
for the operators using that one. When I rewrote RewriteExprTree I accidentally
inverted the logic, resulting in the compacting going down from operators to
operands rather than up from operands to the operators using them, oops. Fix
this, resolving PR12963.
llvm-svn: 159265
|
| |
|
|
| |
llvm-svn: 159264
|
| |
|
|
| |
llvm-svn: 159263
|
| |
|
|
| |
llvm-svn: 159262
|
| |
|
|
|
|
|
|
|
| |
directories from the cmake file. Dunno what the history is here, but
we're not using it.
More refactorings to come here.
llvm-svn: 159261
|
| |
|
|
| |
llvm-svn: 159260
|
| |
|
|
| |
llvm-svn: 159259
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'check-llvm'.
Don't worry! 'check' still works! =] To rationalize the names of targets
used to run tests, the vague plan is the following:
make check-llvm # run LLVM reg/unit tests (currently 'check')
make check-clang # run Clang reg/unit tests (currently 'clang-test')
make check-rt # run CompilerRT reg/unit tests
make check-asan # run ASan reg/unit tests (subset of -rt)
make check-tsan # run TSan reg/unit tests (subset of -rt)
make check-all # run as much of the above as is available
The last one respects what projects are checked out and built for
a given tree. Personally, I would like to eventually make 'check' be an
alias for 'check-all'. For now however, it is an alias for 'check-llvm',
and thus no behavior has changed.
While this patch and my plan only really apply to CMake, I think it
might be good to similarly rationalize the naming scheme for the Make
builds.
llvm-svn: 159258
|
| |
|
|
|
|
| |
instruction
llvm-svn: 159257
|
| |
|
|
|
|
|
| |
add interface for removing a FileEntry from the cache.
Forces a re-read the contents from disk, e.g. because a tool (like cling) wants to pick up a modified file.
llvm-svn: 159256
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
just-built Clang binary, and linking them against the just-built ASan
runtime.
This is *very* brittle. I expect it will require tweaking, and I've
pro-actively disabled it on non-Unix builds and on cross-builds.
It is also currently missing dependency edges on GoogleTest header files
and a few other corner cases, but those can be fixed. This is the major
milestone of a mini-bootstrap-like build of the unittest.
llvm-svn: 159255
|
| |
|
|
| |
llvm-svn: 159254
|
| |
|
|
| |
llvm-svn: 159253
|
| |
|
|
|
|
|
| |
the current version of clang understands __attribute__((unused)) on
fields.
llvm-svn: 159252
|
| |
|
|
| |
llvm-svn: 159251
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
the presence of back references).
I've added an extra FileCheck pass for that with an extra "CURRENT" prefix.
I've carefully chosed the CURRENT/CORRECT prefixes so they
a) are self-descriptive
b) have the same length so the mangling between the current and the correct version is obvious
Feel free to ask me to change the prefixes if you know a better alternative.
llvm-svn: 159250
|
| |
|
|
| |
llvm-svn: 159249
|
| |
|
|
|
|
| |
were broken recently
llvm-svn: 159248
|
| |
|
|
| |
llvm-svn: 159247
|
| |
|
|
| |
llvm-svn: 159246
|
| |
|
|
| |
llvm-svn: 159245
|
| |
|
|
| |
llvm-svn: 159244
|
| |
|
|
| |
llvm-svn: 159243
|
| |
|
|
| |
llvm-svn: 159242
|