| Commit message (Collapse) | Author | Age | Files | Lines | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
continues to
bring in the entire lookup table at once.
Also, give ExternalSemaSource's vtable a home.  This is important because otherwise
any reference to it will cause RTTI to be emitted, and since clang is compiled
with -fno-rtti, that RTTI will contain unresolved references (to ExternalASTSource's
RTTI).  So this change makes it possible to subclass ExternalSemaSource from projects
compiled with RTTI, as long as the subclass's home is compiled with -fno-rtti.
llvm-svn: 105268
 | 
| | 
| 
| 
|  | 
llvm-svn: 105265
 | 
| | 
| 
| 
| 
| 
|  | 
modification.
llvm-svn: 105264
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
associated @interface.
Fixes <rdar://problem/8026215>.
llvm-svn: 105256
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
of isSimpleObjCMessageExpression checks the language,
so change a dynamic check into an assert.
isSimpleObjCMessageExpression is expensive, so only do it
in the common case when it is likely to matter: when the [
of the postfix expr starts on a new line.  This should avoid
doing lookahead for every array expression.
llvm-svn: 105229
 | 
| | 
| 
| 
| 
| 
|  | 
preparation for an alternate mangler.
llvm-svn: 105224
 | 
| | 
| 
| 
|  | 
llvm-svn: 105222
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
a simple, quick check to determine whether the expression starting
with '[' can only be an Objective-C message send. If so, don't parse
it as an array subscript expression. This improves recovery for, e.g.,
  [a method1]
  [a method2]
so that we now produce
  t.m:10:13: error: expected ';' after expression
  [a method]
            ^
instead of some mess about expecting ']'.
llvm-svn: 105221
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
virtual methods.
Please review cdavis, should these methods even be virtual?
llvm-svn: 105218
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
RegionStoreManager::RetrieveElement() that handles indexing into a larger scalar
object to only consult the direct binding of a super region if it is a scalar.
This isn't perfect yet, and a big FIXME is attached to the code.  This causes
the test case for PR 7218 now to pass.
llvm-svn: 105195
 | 
| | 
| 
| 
|  | 
llvm-svn: 105189
 | 
| | 
| 
| 
| 
| 
|  | 
rdar://8042673
llvm-svn: 105188
 | 
| | 
| 
| 
| 
| 
|  | 
been processed, so they don't have to be tip-toed around.
llvm-svn: 105182
 | 
| | 
| 
| 
| 
| 
|  | 
literal. Fixes <rdar://problem/8044135>.
llvm-svn: 105181
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
Parse will need to see these files because it needs to know how to parse
attributes. The generated files are still placed in the appropriate directory so
as to preserve layering. No functional change.
llvm-svn: 105179
 | 
| | 
| 
| 
| 
| 
|  | 
lead to heartache. Fixes <rdar://problem/8044088>.
llvm-svn: 105178
 | 
| | 
| 
| 
|  | 
llvm-svn: 105177
 | 
| | 
| 
| 
|  | 
llvm-svn: 105176
 | 
| | 
| 
| 
| 
| 
| 
|  | 
called function itself is invalid (e.g., because of a semantic error
referring to that declaration). Fixes <rdar://problem/8044142>.
llvm-svn: 105175
 | 
| | 
| 
| 
| 
| 
|  | 
invalid.
llvm-svn: 105172
 | 
| | 
| 
| 
|  | 
llvm-svn: 105171
 | 
| | 
| 
| 
| 
| 
|  | 
'IsClangAttr' to match prevailing style in this file. Patch by Jon Mulder!
llvm-svn: 105170
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The macros required for DeclNodes use have changed to match the use of
StmtNodes. The FooFirst enumerator constants have been named firstFoo
to match usage elsewhere.
llvm-svn: 105165
 | 
| | 
| 
| 
|  | 
llvm-svn: 105162
 | 
| | 
| 
| 
| 
| 
|  | 
the previous code. However, it still has quadratic performance, something which I intend to fix shortly in a subsequent patch.
llvm-svn: 105161
 | 
| | 
| 
| 
| 
| 
|  | 
potentially-NULL "function" argument.
llvm-svn: 105152
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
isn't possible to compute.
This patch is mostly refactoring; the key change is the addition of the code
starting with the comment, "Check whether the function has a computable LLVM
signature."  The solution here is essentially the same as the way the
vtable code handles such functions.
llvm-svn: 105151
 | 
| | 
| 
| 
|  | 
llvm-svn: 105137
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
type that we expect to see at a given point in the grammar, e.g., when
initializing a variable, returning a result, or calling a function. We
don't prune the candidate set at all, just adjust priorities to favor
things that should type-check, using an ultra-simplified type system.
llvm-svn: 105128
 | 
| | 
| 
| 
|  | 
llvm-svn: 105116
 | 
| | 
| 
| 
|  | 
llvm-svn: 105114
 | 
| | 
| 
| 
|  | 
llvm-svn: 105113
 | 
| | 
| 
| 
| 
| 
|  | 
functionality change.
llvm-svn: 105112
 | 
| | 
| 
| 
|  | 
llvm-svn: 105111
 | 
| | 
| 
| 
| 
| 
|  | 
Instead of doing it as a separate step, we now use the BaseSubobjectInfo and use it when laying out the bases. This fixes a bug where we would either not add a primary virtual base at all, or add it at the wrong offset.
llvm-svn: 105110
 | 
| | 
| 
| 
|  | 
llvm-svn: 105104
 | 
| | 
| 
| 
| 
| 
|  | 
BaseSubobjectInfo. No functionality change.
llvm-svn: 105103
 | 
| | 
| 
| 
| 
| 
|  | 
RecordLayoutBuilder because we're going to need it to be able to correctly add offsets for primary virtual bases.
llvm-svn: 105102
 | 
| | 
| 
| 
|  | 
llvm-svn: 105099
 | 
| | 
| 
| 
|  | 
llvm-svn: 105097
 | 
| | 
| 
| 
|  | 
llvm-svn: 105084
 | 
| | 
| 
| 
|  | 
llvm-svn: 105083
 | 
| | 
| 
| 
|  | 
llvm-svn: 105082
 | 
| | 
| 
| 
| 
| 
|  | 
valgrind problems.
llvm-svn: 105062
 | 
| | 
| 
| 
| 
| 
|  | 
generate a proper header.
llvm-svn: 105058
 | 
| | 
| 
| 
|  | 
llvm-svn: 105013
 | 
| | 
| 
| 
| 
| 
|  | 
(radar 8040068).
llvm-svn: 105011
 | 
| | 
| 
| 
|  | 
llvm-svn: 105010
 | 
| | 
| 
| 
|  | 
llvm-svn: 105007
 | 
| | 
| 
| 
|  | 
llvm-svn: 105002
 |