| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
The (new) CoverageMapping/macroparams.c test is failing on a number of
buildbots. Reverting it until Alex can investigate and fix the test.
llvm-svn: 215274
|
| |
|
|
| |
llvm-svn: 215273
|
| |
|
|
|
|
|
| |
imported it from a module when performing finalization before writing out
an AST file.
llvm-svn: 215272
|
| |
|
|
|
|
| |
created.
llvm-svn: 215271
|
| |
|
|
|
|
|
| |
This will lower them using register copies rather than loads and stores
to the stack.
llvm-svn: 215270
|
| |
|
|
|
|
|
|
|
|
|
|
| |
These tests were using SI-NOT: MOVREL to make sure concat vectors
weren't being lowered to stack loads and stores, but we are using
scratch buffers for the stack now instead of registers, so we need
to add an additional SI-NOT check for scratch buffers.
With this change I was able to uncover one broken test which will
be fixed in a future commit.
llvm-svn: 215269
|
| |
|
|
|
|
|
|
|
| |
class Module. It's almost always going to be the same as
getContainingModule() for top-level modules, so just add a map to cover
the remaining cases. This lets us do less bookkeeping to keep the
ModuleMap fields up to date.
llvm-svn: 215268
|
| |
|
|
| |
llvm-svn: 215267
|
| |
|
|
| |
llvm-svn: 215266
|
| |
|
|
|
|
| |
This appears to have been a copy / paste error.
llvm-svn: 215265
|
| |
|
|
| |
llvm-svn: 215264
|
| |
|
|
|
|
|
|
| |
This function might be a bit easier if it were split in two with a lot
of early returns - and that setOptional bit in the outer function, but
anyway.
llvm-svn: 215263
|
| |
|
|
| |
llvm-svn: 215262
|
| |
|
|
|
|
|
|
|
|
| |
This patch adds the tests for the coverage mapping generation.
Most of the tests check the mapping regions produced by
the generator, and one checks the llvm IR.
Differential Revision: http://reviews.llvm.org/D4793
llvm-svn: 215261
|
| |
|
|
|
|
| |
Patch by Jim Grosbach.
llvm-svn: 215260
|
| |
|
|
|
|
|
|
|
| |
These macros are used as markers for Interface Builder and need to be defined
to empty strings since they have no impact on the code.
Patch by Ted Kremenek.
llvm-svn: 215259
|
| |
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D4799
llvm-svn: 215258
|
| |
|
|
|
|
|
|
|
|
|
|
| |
indirection.
Summary: I was going to fix the use of raw pointer ownership in "takeGraph" when I realized that function was unused and the whole ExplodedGraph could just be owned by value without the std::unique_ptr indirection at all.
Reviewers: jordan_rose
Differential Revision: http://reviews.llvm.org/D4833
llvm-svn: 215257
|
| |
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D4826
Reviewed by: Enrico Granata
llvm-svn: 215256
|
| |
|
|
|
|
|
|
|
|
|
| |
Cleanup only: no functional change.
This patch makes RuntimeDyldMachO targets directly responsible for decoding
immediates, rather than letting them implement catch a callback from generic
code. Since this is a very target specific operation, it makes sense to let the
target-specific code drive it.
llvm-svn: 215255
|
| |
|
|
| |
llvm-svn: 215253
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This flag can be used to force linking of CXX-specific parts
of sanitizer runtimes into the final executable. It gives more precise
control than --driver-mode=g++ and comes handy when user links several
object files with sanitized C++ code into an executable, but wants
to provide libstdc++ himself, instead of relying on Clang dirver's
behavior.
Test Plan: clang regression test suite
Reviewers: chandlerc, rsmith
Reviewed By: rsmith
Subscribers: cfe-commits
Differential Revision: http://reviews.llvm.org/D4824
llvm-svn: 215252
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
macro arguments.
Previously, these warnings skipped any code in a macro expansion. Preform an
additional check and warn when the expression and context locations are both
in the macro argument.
The most obvious case not caught is passing a pointer directly to a macro,
i.e 'assert(&array)' but 'assert(&array && "valid array")' is caught. This is
because macro arguments are not typed and the conversion happens inside the
macro.
llvm-svn: 215251
|
| |
|
|
|
|
|
| |
use mis-cased property name (which is currently accepted silently
due to the way property setters are named). rdar://17911746
llvm-svn: 215250
|
| |
|
|
|
|
| |
Sorry for the noise.
llvm-svn: 215249
|
| |
|
|
| |
llvm-svn: 215248
|
| |
|
|
|
|
|
|
| |
a given platform in a top-level CMakeLists.txt to use it both
in lib/ and in test/ subdirectories. Move architecture/platform
checks to config-ix.
llvm-svn: 215247
|
| |
|
|
| |
llvm-svn: 215246
|
| |
|
|
|
|
|
|
| |
The previous encoding only allowed a single digit for the minor version
number. This changes it to use 2 digits for both the minor version and the
revision number.
llvm-svn: 215245
|
| |
|
|
|
|
|
|
|
|
|
|
| |
EvaluateExpression
from Python. If you don't need to refer to the result in another expression, there's no
need to bloat the persistent variable table with them since you already have the result
SBValue to work with.
<rdar://problem/17963645>
llvm-svn: 215244
|
| |
|
|
| |
llvm-svn: 215243
|
| |
|
|
|
|
|
| |
llvm::sys::path::native has a superset of the functionality and this was the
only use of llvm::sys::fs::normalize_separators.
llvm-svn: 215242
|
| |
|
|
|
|
| |
Part of pr20544. Test to follow in a second.
llvm-svn: 215241
|
| |
|
|
| |
llvm-svn: 215240
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
allocation range
in all but one of the AllocatedBlocks that matched the requested permissions.
Over time this would make the performance of expressions slow down considerably.
Also added a little bit of logging that was helpful in resolving the issue.
<rdar://problem/17954438>
llvm-svn: 215239
|
| |
|
|
|
|
| |
empty functions will assert in the MC object writer.
llvm-svn: 215238
|
| |
|
|
|
|
|
|
| |
I accidentally also used INC/DEC for unsigned arithmetic which doesn't work,
because INC/DEC don't set the required flag which is used for the overflow
check.
llvm-svn: 215237
|
| |
|
|
|
|
|
|
| |
It wasn't actually a bug that -mabicalls/-mno-abicalls wasn't being passed to
GAS. The only reason we pass it to the integrated assembler is because it shares
the same framework with CodeGen.
llvm-svn: 215236
|
| |
|
|
|
|
| |
rdar://17554063
llvm-svn: 215235
|
| |
|
|
| |
llvm-svn: 215234
|
| |
|
|
|
|
|
|
| |
std::map invalidates the iterator to any element that gets deleted, which means
we can't increment it correctly afterwards. This was causing Darwin test
failures.
llvm-svn: 215233
|
| |
|
|
|
|
|
| |
for building Objective-C array literals in ARC
mode. rdar://17554063
llvm-svn: 215232
|
| |
|
|
| |
llvm-svn: 215231
|
| |
|
|
|
|
|
|
|
|
| |
intrinsics.
This is a small peephole optimization to emit INC/DEC when possible.
Fixes <rdar://problem/17952308>.
llvm-svn: 215230
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
the --use-cc option.
Instead, we will search in the PATH
For example:
scan-build --use-cc=arm-none-eabi-gcc -o out make -e
Initially reported as a Debian Bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748777
llvm-svn: 215229
|
| |
|
|
|
|
|
|
|
| |
the assertion that no argument variable is overwritten by subsequent argument variables.
This turned up a bug in clang where arguments were emitted with
duplicate argument numbers (see r215227).
llvm-svn: 215228
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the debug info argument numbering.
Due to the possible presence of return-by-out parameters, using the LLVM
argument number count when numbering debug info arguments can end up
off-by-one. This could produce two arguments with the same number, which
would in turn cause LLVM to emit only one of those arguments (whichever
it found last) or assert (r215157).
llvm-svn: 215227
|
| |
|
|
| |
llvm-svn: 215226
|
| |
|
|
|
|
| |
I supposed PRIx32 might be unused in the tree.
llvm-svn: 215225
|
| |
|
|
| |
llvm-svn: 215224
|