| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
refactorings in that revision, and some of the subsequent bugfixes, which
seem to be relevant even without delayed exception specification parsing.
llvm-svn: 156031
|
| |
|
|
|
|
| |
expressions.
llvm-svn: 156030
|
| |
|
|
|
|
| |
just like it now knows for FMULs.
llvm-svn: 156029
|
| |
|
|
|
|
|
| |
and Hybrid for 32 bit, since benchmarks show ILP scheduling is better
most of the time.
llvm-svn: 156028
|
| |
|
|
|
|
| |
Patches by Csaba Raduly (rcsaba@gmail.com)
llvm-svn: 156027
|
| |
|
|
|
|
|
| |
classes/structs that have variable-length arrays at
the end.
llvm-svn: 156026
|
| |
|
|
|
|
| |
Lincroft and Medfield.
llvm-svn: 156025
|
| |
|
|
| |
llvm-svn: 156023
|
| |
|
|
| |
llvm-svn: 156022
|
| |
|
|
| |
llvm-svn: 156021
|
| |
|
|
| |
llvm-svn: 156020
|
| |
|
|
| |
llvm-svn: 156019
|
| |
|
|
| |
llvm-svn: 156018
|
| |
|
|
| |
llvm-svn: 156017
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
walk
them, otherwise we cannot produce an error for both
struct HIDDEN test4; // canonical
struct test4;
struct DEFAULT test4;
and
struct test5; // canonical
struct HIDDEN test5;
struct DEFAULT test5;
llvm-svn: 156016
|
| |
|
|
| |
llvm-svn: 156009
|
| |
|
|
| |
llvm-svn: 156008
|
| |
|
|
| |
llvm-svn: 156007
|
| |
|
|
| |
llvm-svn: 156005
|
| |
|
|
|
|
|
| |
related to laying out ivar structs and accessing non-fragile-ivar
in more compilated cases. // rdar://11323187
llvm-svn: 156004
|
| |
|
|
|
|
|
|
| |
TableGen-generated StringMatcher, for a 1.2% speedup in -fparse-only
time in <rdar://problem/11004361>. Thanks to Benjamin for pointing me
at StringMatcher!
llvm-svn: 156003
|
| |
|
|
|
|
| |
be used by clang-tblgen.
llvm-svn: 156000
|
| |
|
|
|
|
| |
we accept are not modeled somehow via Attr.td.
llvm-svn: 155998
|
| |
|
|
|
|
|
|
|
| |
This avoids warnings when included in a application that
uses -Wstrict-prototypes.
e.g: AsmPrinters.def:27:1: warning: function declaration isn't a prototype [-Wstrict-prototypes]
llvm-svn: 155997
|
| |
|
|
|
|
| |
by providing the latencies for the instructions in X86InstrFPStack.td.
llvm-svn: 155996
|
| |
|
|
|
|
| |
as an AST node, and fold a number of such attributes into Attr.td.
llvm-svn: 155995
|
| |
|
|
| |
llvm-svn: 155994
|
| |
|
|
|
|
|
|
|
|
| |
Without the '<' prefix in the doxycomment these comments were incorrectly
attached to the proceeding comment on the next line, rather than the
preceeding one.
Fixes PR12722
llvm-svn: 155993
|
| |
|
|
|
|
|
|
| |
The commit is intended to fix rdar://10961709.
But it is the root cause of PR12720.
Revert it for now.
llvm-svn: 155992
|
| |
|
|
|
|
|
| |
and const (as "__const") using tblgen, rather than explicitly hacking
them in.
llvm-svn: 155991
|
| |
|
|
|
|
|
|
|
|
|
| |
and disable it by default on more platforms.
For now -fno-math-errno is the default on BSD-derived platforms (Darwin,
DragonFlyBSD, FreeBSD, NetBSD, OpenBSD). If the default is not right for
your platform, please yell. I only verified the result with the default
compilers on Darwin and FreeBSD.
llvm-svn: 155990
|
| |
|
|
|
|
| |
Benjamin has suggested a better approach.
llvm-svn: 155989
|
| |
|
|
|
|
|
| |
we're looking at a normal token. Tiny positive impact -fsyntax-only
time for <rdar://problem/11004361>.
llvm-svn: 155988
|
| |
|
|
|
|
|
| |
IdentifierInfo *) with a static StringMap, improving -fsyntax-only
performance by 1% for the example in <rdar://problem/11004361>.
llvm-svn: 155987
|
| |
|
|
| |
llvm-svn: 155986
|
| |
|
|
|
|
|
| |
methods. Use a weak value handle to keep up with this.
PR12245
llvm-svn: 155984
|
| |
|
|
| |
llvm-svn: 155983
|
| |
|
|
|
|
| |
for AsmPrinter.
llvm-svn: 155982
|
| |
|
|
|
|
|
|
| |
-fpack-struct's handling has changed in CC1 (one of only two flags that needed changing) because the driver treats "-fpack-struct" as a boolean flag, and CC1 (did) treat it as an option with a separated value.
This change causes -fpack-struct=X to be forwarded correctly to -fpack-struct=X instead of erroneously to "-fpack-struct X"
llvm-svn: 155981
|
| |
|
|
|
|
|
| |
allowed, and it'll blow up in unfortunate ways when using a proper
C++11 library.
llvm-svn: 155980
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Note that support for rvalue references does not imply support
for the full set of move-related STL operations.
I've preserved support for an odd little thing in insert() where
we're trying to support inserting a new element from an existing
one. If we actually want to support that, there's a lot more we
need to do: insert can call either grow or push_back, neither of
which is safe against this particular use pattern.
llvm-svn: 155979
|
| |
|
|
| |
llvm-svn: 155978
|
| |
|
|
| |
llvm-svn: 155977
|
| |
|
|
|
|
| |
the MachO spec.
llvm-svn: 155976
|
| |
|
|
|
|
|
| |
the parsing of such things appears to be a conforming extension, but it breaks
libstdc++4.7's std::pair.
llvm-svn: 155975
|
| |
|
|
|
|
| |
Really just a wild stab in the dark.
llvm-svn: 155974
|
| |
|
|
|
|
| |
to use "--" to terminate the options.
llvm-svn: 155973
|
| |
|
|
|
|
|
|
|
|
|
| |
reverse track interesting
values through interesting expressions. This allows us to map from interesting values in a caller
to interesting values in a caller, thus recovering some precision in diagnostics lost from IPA.
Fixes <rdar://problem/11327497>
llvm-svn: 155971
|
| |
|
|
|
|
|
|
| |
replace them with
includes of ClangUserExpression that were being errantly dragged in through same.
llvm-svn: 155970
|
| |
|
|
|
|
|
|
|
| |
* Work around build failures due to gcc 4.2 bugs.
* Remove BodyIndexer::TraverseCXXOperatorCallExpr, which was not being called
prior to this change, and whose presence disables a RecursiveASTVisitor
stack space optimization after this change.
llvm-svn: 155969
|