| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
in clang r176726. Fix the build of lldb
llvm-svn: 176790
|
| |
|
|
|
|
| |
vec_lvewx according to AltiVec Programming Interface Manual
llvm-svn: 176789
|
| |
|
|
|
|
|
|
|
|
| |
Before: clang-3: error: no input files
After: clang-3.3: error: no input files
This means that we'll also print clang.exe on windows, but I don't see a problem
with that.
llvm-svn: 176788
|
| |
|
|
| |
llvm-svn: 176787
|
| |
|
|
|
|
| |
memory on stack, and memcpy the actual value before the call.
llvm-svn: 176786
|
| |
|
|
| |
llvm-svn: 176785
|
| |
|
|
| |
llvm-svn: 176784
|
| |
|
|
| |
llvm-svn: 176783
|
| |
|
|
| |
llvm-svn: 176782
|
| |
|
|
| |
llvm-svn: 176781
|
| |
|
|
|
|
| |
6.4.4.4/1 and 6.4.5/1.
llvm-svn: 176780
|
| |
|
|
|
|
|
|
| |
handle raw string literals here. C++11 doesn't yet specify how they will
behave, but discussion on core suggests that we should just strip off
everything but the r-char-sequence.
llvm-svn: 176779
|
| |
|
|
|
|
| |
variable to be a local variable in the only method that uses it.
llvm-svn: 176778
|
| |
|
|
|
|
|
|
|
| |
intrinsic - it can cause impossible-to-schedule subgraphs to be
introduced.
PR15053.
llvm-svn: 176777
|
| |
|
|
| |
llvm-svn: 176776
|
| |
|
|
|
|
|
| |
This made us emit runtime checks in a random order. Hopefully bootstrap
miscompares will go away now.
llvm-svn: 176775
|
| |
|
|
| |
llvm-svn: 176774
|
| |
|
|
| |
llvm-svn: 176773
|
| |
|
|
| |
llvm-svn: 176772
|
| |
|
|
| |
llvm-svn: 176771
|
| |
|
|
| |
llvm-svn: 176770
|
| |
|
|
|
|
| |
Ignore all DbgIntriniscInfo instructions instead of just DbgValueInst.
llvm-svn: 176769
|
| |
|
|
|
|
|
|
|
| |
We want vectorization to happen at -g. Ignore calls to the dbg.value intrinsic
and don't transfer them to the vectorized code.
radar://13378964
llvm-svn: 176768
|
| |
|
|
| |
llvm-svn: 176767
|
| |
|
|
|
|
|
|
| |
The strlen+memcmp was hidden in a call to StringRef::operator==. We check if
there are any null bytes in the string upfront so we can simplify the comparison
Small speedup when compiling code with many function calls.
llvm-svn: 176766
|
| |
|
|
| |
llvm-svn: 176765
|
| |
|
|
|
|
| |
r176751. Also, learn a lesson about applying patches by hand/eyeball.
llvm-svn: 176764
|
| |
|
|
| |
llvm-svn: 176763
|
| |
|
|
|
|
| |
for choosing to emit a shndx was simply testing the wrong variable.
llvm-svn: 176762
|
| |
|
|
|
|
|
|
| |
DNBArchImplARM. This framework is no longer around;
all armv7 devices support using hardware breakpoints
to instruction single step.
llvm-svn: 176761
|
| |
|
|
|
|
| |
debugserver's build settings.
llvm-svn: 176760
|
| |
|
|
|
|
|
| |
Also, don't build debugserver with -DUSE_ARM_DISASSEMBLER_FRAMEWORK -
that framework isn't around at this point.
llvm-svn: 176759
|
| |
|
|
| |
llvm-svn: 176758
|
| |
|
|
|
|
|
| |
Each transform belongs in its own sub-page now. Minor refactoring to reflect
new heading levels.
llvm-svn: 176757
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
same node it was registered at
The visitor used to assume that the value it’s tracking is null in the first node it examines. This is not true.
If we are registering the Suppress Inlined Defensive checks visitor while traversing in another visitor
(such as FindlastStoreVisitor). When we restart with the IDC visitor, the invariance of the visitor does
not hold since the symbol we are tracking no longer exists at that point.
I had to pass the ErrorNode when creating the IDC visitor, because, in some cases, node N is
neither the error node nor will be visible along the path (we had not finalized the path at that point
and are dealing with ExplodedGraph.)
We should revisit the other visitors which might not be aware that they might get nodes, which are
later in path than the trigger point.
This suppresses a number of inline defensive checks in JavaScriptCore.
llvm-svn: 176756
|
| |
|
|
| |
llvm-svn: 176755
|
| |
|
|
|
|
| |
This tests that we track the original Expr if getDerefExpr fails.
llvm-svn: 176754
|
| |
|
|
| |
llvm-svn: 176753
|
| |
|
|
|
|
|
|
| |
As much as I hate to leave this hacky code in that adds some d and q registers to ARM registers, I must leave it in.
The code is now fixed to not just assume ANY arm target will have registers in a certain order. We now verify the common regs are the same name and byte size before adding the d and q regs.
llvm-svn: 176752
|
| |
|
|
|
|
| |
Count the subprograms, not the compile units.
llvm-svn: 176751
|
| |
|
|
|
|
|
| |
an assertion due to non-implicit Objective-C methods
without source locations.
llvm-svn: 176750
|
| |
|
|
| |
llvm-svn: 176749
|
| |
|
|
| |
llvm-svn: 176748
|
| |
|
|
|
|
| |
This only happens when the section header count is > 1024.
llvm-svn: 176747
|
| |
|
|
|
|
|
|
| |
it. Fortunately, versions of gcov that predate the extra checksum also ignore
any extra data, so this isn't a problem. This matches the API change made in
r176745.
llvm-svn: 176746
|
| |
|
|
|
|
|
|
| |
it. Fortunately, versions of gcov that predate the extra checksum also ignore
any extra data, so this isn't a problem. There will be a matching commit in
compiler-rt.
llvm-svn: 176745
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, MallocChecker's pointer escape check and its post-call state
update for Objective-C method calls had a fair amount duplicated logic
and not-entirely-consistent checks. This commit restructures all this to
be more consistent and possibly allow us to be more aggressive in warning
about double-frees.
New policy (applies to system header methods only):
(1) If this is a method we know about, model it as taking/holding ownership
of the passed-in buffer.
(1a) ...unless there's a "freeWhenDone:" parameter with a zero (NO) value.
(2) If there's a "freeWhenDone:" parameter (but it's not a method we know
about), treat the buffer as escaping if the value is non-zero (YES) and
non-escaping if it's zero (NO).
(3) If the first selector piece ends with "NoCopy" (but it's not a method we
know about and there's no "freeWhenDone:" parameter), treat the buffer
as escaping.
The reason that (2) and (3) don't explicitly model the ownership transfer is
because we can't be sure that they will actually free the memory using free(),
and we wouldn't want to emit a spurious "mismatched allocator" warning
(coming in Anton's upcoming patch). In the future, we may have an idea of a
"generic deallocation", i.e. we assume that the deallocator is correct but
still continue tracking the region so that we can warn about double-frees.
Patch by Anton Yartsev, with modifications from me.
llvm-svn: 176744
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that it looks through certain syntactic forms and applies
even if normal inference would have succeeded.
There is potential for source incompatibility from this
change, but overall we feel that it produces a much
cleaner and more defensible result, and the block
compatibility rules should curb a lot of the potential
for annoyance.
rdar://13200889
llvm-svn: 176743
|
| |
|
|
|
|
| |
is non-anonymous or is defined in a typedef of itself.
llvm-svn: 176742
|
| |
|
|
|
|
| |
Add a missing "break" in processing the -h option to "breakpoint set".
llvm-svn: 176741
|