| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This was regression from r134829. When linking we have to be conservative. If
one of the symbols has a significant address, then the result should have it
too.
llvm-svn: 189935
|
|
|
|
| |
llvm-svn: 189934
|
|
|
|
| |
llvm-svn: 189933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes sure we produce the right number of unwrapped lines,
a follow-up patch will make the whitespace formatting consistent.
Before:
void f() {
int i = {[operation setCompletionBlock : ^{ [self onOperationDone];
}]
}
;
}
After:
void f() {
int i = {[operation setCompletionBlock : ^{
[self onOperationDone];
}] };
}
llvm-svn: 189932
|
|
|
|
|
|
|
|
|
|
| |
"(icmp op i8 A, B)" is equivalent to "(icmp op i8 (A & 0xff), B)" as a
degenerate case. Allowing this as a "masked" comparison when analysing "(icmp)
&/| (icmp)" allows us to combine them in more cases.
rdar://problem/7625728
llvm-svn: 189931
|
|
|
|
|
|
|
|
|
|
|
| |
Even in cases which aren't universally optimisable like "(A & B) != 0 && (A &
C) != 0", the masks can make one of the comparisons completely redundant. In
this case, since we've gone to the effort of spotting masked comparisons we
should combine them.
rdar://problem/7625728
llvm-svn: 189930
|
|
|
|
|
|
| |
in UAR mode
llvm-svn: 189929
|
|
|
|
| |
llvm-svn: 189928
|
|
|
|
|
|
| |
tweaking expressions.
llvm-svn: 189927
|
|
|
|
|
|
|
|
|
|
| |
instructions:
sshr,ushr,ssra,usra,srshr,urshr,srsra,ursra,sri,shl,sli,sqshlu,sqshl,uqshl,shrn,sqrshr$
and 4 convert instructions:
scvtf,ucvtf,fcvtzs,fcvtzu
llvm-svn: 189926
|
|
|
|
|
|
|
|
|
|
| |
instructions:
sshr,ushr,ssra,usra,srshr,urshr,srsra,ursra,sri,shl,sli,sqshlu,sqshl,uqshl,shrn,sqrshrun,sqshrn,uqshr,sqrshrn,uqrshrn,sshll,ushll
and 4 convert instructions:
scvtf,ucvtf,fcvtzs,fcvtzu
llvm-svn: 189925
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
int c = [ &, &a, a]{
[ =, c, &d]{
return b++;
}();
}();
After:
int c = [&, &a, a] {
[=, c, &d] {
return b++;
}();
}();
llvm-svn: 189924
|
|
|
|
| |
llvm-svn: 189923
|
|
|
|
| |
llvm-svn: 189922
|
|
|
|
|
|
| |
comparison warning.
llvm-svn: 189921
|
|
|
|
|
|
| |
gdb.
llvm-svn: 189920
|
|
|
|
| |
llvm-svn: 189919
|
|
|
|
| |
llvm-svn: 189918
|
|
|
|
| |
llvm-svn: 189917
|
|
|
|
|
|
|
| |
If source code is invalid, error recovery can lead to name lookup in a set containing invalid declaration. The lookup is stopped once found such declaration, but LookupResult object could remain in inconsistent state. Its destructor triggered a check, which caused assert violation.
This patch fixes PR16964 and PR12791.
llvm-svn: 189916
|
|
|
|
|
|
| |
info that support what Eric calls "the member hack".
llvm-svn: 189915
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dead and the rest of the compatibility should be done on a dwarf-N level.""
This reverts commit r189913.
Talked with Eric on IRC. I am going to XFAIL the failing test since it
is using what Eric described as "the member hack" which was needed on
that old GDB.
Sorry for the noise!
llvm-svn: 189914
|
|
|
|
|
|
|
|
|
|
|
|
| |
the rest of the compatibility should be done on a dwarf-N level."
This reverts commit r189903.
This commit broke the phase 1 buildbot for a while.
http://lab.llvm.org:8013/builders/clang-x86_64-darwin11-nobootstrap-RAincremental/builds/6684
llvm-svn: 189913
|
|
|
|
| |
llvm-svn: 189912
|
|
|
|
|
|
|
|
|
|
| |
Iterator of std::vector may be implemented as a raw pointer. In
this case begin iterators are rvalues and cannot be incremented.
For example, this is the case with STDCXX implementation of vector.
Patch by Konstantin Tokarev <annulen@yandex.ru>.
llvm-svn: 189911
|
|
|
|
| |
llvm-svn: 189910
|
|
|
|
| |
llvm-svn: 189909
|
|
|
|
|
|
|
|
|
| |
it to refer to castAs/getAs.
The original change to remove the (broken) cast/dyn_cast support from TypeLoc
was in r175462. (Thanks to David Blaikie for the reference.)
llvm-svn: 189908
|
|
|
|
|
|
|
|
|
|
| |
It looks like there is a possibility of seeing RO/RW note sections
and we would need to create an appropriate RO/RW segment associated
with them.
Adds a test too.
llvm-svn: 189907
|
|
|
|
|
|
|
|
|
|
|
| |
we have a more principled approach (the 'requires complete type' callback)"
This reverts commit r189013.
This is causing a segfault crash in a test case I have. Reverting while
I investigate the issue.
llvm-svn: 189906
|
|
|
|
|
|
| |
\param should be used to describe individual parameters. Use a command like \a or \c for visual enhancements.
llvm-svn: 189905
|
|
|
|
|
|
| |
Investigating.
llvm-svn: 189904
|
|
|
|
|
|
| |
the rest of the compatibility should be done on a dwarf-N level.
llvm-svn: 189903
|
|
|
|
|
|
| |
in the module. Add a FIXME with a comment about darwin's ld.
llvm-svn: 189902
|
|
|
|
| |
llvm-svn: 189901
|
|
|
|
| |
llvm-svn: 189900
|
|
|
|
| |
llvm-svn: 189899
|
|
|
|
|
|
|
|
| |
I tried to implement this properly in r189051, but I didn't have enough
test coverage. Richard kindly provided more test cases than I could
possibly imagine and now we should have the correct condition.
llvm-svn: 189898
|
|
|
|
|
|
|
|
|
|
|
| |
The compiler is allowed to add a linker option starting with -?<name> to
.drectve section. If the linker can interpret -<name>, it's processed as if
there's no question mark there. If not, such option is silently ignored.
This is a COFF's feature to allow the compiler to emit new linker options
while keeping compatibility with older linkers.
llvm-svn: 189897
|
|
|
|
|
|
|
|
| |
Emit note sections if the input contains a note section.
Also emit a note segment.
llvm-svn: 189896
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this patch, name of driver implementation is not consistent with its
option table file. Specifically, LDOptions has a different prefix than
GnuLdDriver.
This patch renames option files, so that the option files have the same prefix
as the corresponding driver files.
Differential Revision: http://llvm-reviews.chandlerc.com/D1591
llvm-svn: 189895
|
|
|
|
| |
llvm-svn: 189894
|
|
|
|
|
|
| |
explicit template instantiation" warning.
llvm-svn: 189893
|
|
|
|
|
|
|
| |
ObjectiveC methods. Apply specific annotations for them
instead as determined by the static analyzer.
llvm-svn: 189892
|
|
|
|
| |
llvm-svn: 189891
|
|
|
|
| |
llvm-svn: 189890
|
|
|
|
|
|
|
|
| |
Instead of directly manipulating the thread list in Launch and Attach,
just rely on RefreshStateAfterStop to populate the initial list.
Review: http://llvm-reviews.chandlerc.com/D1565
llvm-svn: 189889
|
|
|
|
| |
llvm-svn: 189888
|
|
|
|
|
|
|
| |
Also add a llvm_unreachable call so that the linker will trip on unhandled
inputElement types.
llvm-svn: 189887
|
|
|
|
|
|
|
|
|
|
| |
Original message:
If a constant or a function has linkonce_odr linkage and unnamed_addr, mark
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: 189886
|