- Apr 22, 2010
-
-
Devang Patel authored
llvm-svn: 102033
-
Douglas Gregor authored
Objective-C++ have a more complex grammar than in Objective-C (surprise!), because (1) The receiver of an instance message can be a qualified name such as ::I or identity<I>::type. (2) Expressions in C++ can start with a type. The receiver grammar isn't actually ambiguous; it just takes a bit of work to parse past the type before deciding whether we have a type or expression. We do this in two places within the grammar: once for message sends and once when we're determining whether a []'d clause in an initializer list is a message send or a C99 designated initializer. This implementation of Objective-C++ message sends contains one known extension beyond GCC's implementation, which is to permit a typename-specifier as the receiver type for a class message, e.g., [typename compute_receiver_type<T>::type method]; Note that the same effect can be achieved in GCC by way of a typedef, e.g., typedef typename computed_receiver_type<T>::type Computed; [Computed method]; so this is merely a convenience. Note also that message sends still cannot involve dependent types or values. llvm-svn: 102031
-
- Apr 21, 2010
-
-
Douglas Gregor authored
Objective-C class message expression into a type from the parser (which was doing so in two places) to Action::getObjCMessageKind() which, in the case of Sema, reduces the number of name lookups we need to perform. llvm-svn: 102026
-
Anders Carlsson authored
llvm-svn: 102025
-
Douglas Gregor authored
to reduce nesting. No functionality change. llvm-svn: 102022
-
Douglas Gregor authored
sends. Major changes include: - Expanded the interface from two actions (ActOnInstanceMessage, ActOnClassMessage), where ActOnClassMessage also handled sends to "super" by checking whether the identifier was "super", to three actions (ActOnInstanceMessage, ActOnClassMessage, ActOnSuperMessage). Code completion has the same changes. - The parser now resolves the type to which we are sending a class message, so ActOnClassMessage now accepts a TypeTy* (rather than an IdentifierInfo *). This opens the door to more interesting types (for Objective-C++ support). - Split ActOnInstanceMessage and ActOnClassMessage into parser action functions (with their original names) and semantic functions (BuildInstanceMessage and BuildClassMessage, respectively). At present, this split is onyl used by ActOnSuperMessage, which decides which kind of super message it has and forwards to the appropriate Build*Message. In the future, Build*Message will be used by template instantiation. - Use getObjCMessageKind() within the disambiguation of Objective-C message sends vs. array designators. Two notes about substandard bits in this patch: - There is some redundancy in the code in ParseObjCMessageExpr and ParseInitializerWithPotentialDesignator; this will be addressed shortly by centralizing the mapping from identifiers to type names for the message receiver. - There is some #if 0'd code that won't likely ever be used---it handles the use of 'super' in methods whose class does not have a superclass---but could be used to model GCC's behavior more closely. This code will die in my next check-in, but I want it in Subversion. llvm-svn: 102021
-
Anders Carlsson authored
Keep tack of whether a base in an InitializedEntity is an inherited virtual base or not. Use this in CheckConstructorAccess. llvm-svn: 102020
-
Daniel Dunbar authored
exceeds the minimum ABI alignment. llvm-svn: 102019
-
Daniel Dunbar authored
llvm-svn: 102018
-
Daniel Dunbar authored
llvm-svn: 102016
-
Daniel Dunbar authored
llvm-svn: 102015
-
Daniel Dunbar authored
non-bit-fields). llvm-svn: 102014
-
Fariborz Jahanian authored
property synthesis is using a super class ivar. llvm-svn: 102011
-
Anders Carlsson authored
Pass the InitializedEntity to Sema::CheckConstructorAccess and use it to report different diagnostics depending on which entity is being initialized. llvm-svn: 102010
-
Anders Carlsson authored
llvm-svn: 102007
-
Fariborz Jahanian authored
llvm-svn: 102005
-
Benjamin Kramer authored
llvm-svn: 101999
-
John McCall authored
because EmitBranch actually clears the insert point. This version actually accomplishes what I initially wanted. llvm-svn: 101998
-
John McCall authored
(if there's a current block). The chief advantage of doing this is that it lets us pick blocks (e.g. EH blocks) to push to the end of the function so that fallthrough happens consistently --- i.e. it gives us the flexibility of ordering blocks as we please without having to change the order in which we generate code. There are standard (?) optimization passes which can do some of that for us, but better to generate reasonable code to begin with. llvm-svn: 101997
-
John McCall authored
just to save the current insertion state! This change significantly simplifies the IR CFG in exceptions code. llvm-svn: 101996
-
Zhongxing Xu authored
llvm-svn: 101994
-
Douglas Gregor authored
and only define it where we know we need it---Linux and Cygwin. Thanks to Chris for the prodding. llvm-svn: 101989
-
Douglas Gregor authored
llvm-svn: 101988
-
Zhongxing Xu authored
llvm-svn: 101983
-
John McCall authored
llvm-svn: 101982
-
Zhongxing Xu authored
llvm-svn: 101981
-
Zhongxing Xu authored
llvm-svn: 101980
-
Douglas Gregor authored
expressions, to improve source-location information, clarify the actual receiver of the message, and pave the way for proper C++ support. The ObjCMessageExpr node represents four different kinds of message sends in a single AST node: 1) Send to a object instance described by an expression (e.g., [x method:5]) 2) Send to a class described by the class name (e.g., [NSString method:5]) 3) Send to a superclass class (e.g, [super method:5] in class method) 4) Send to a superclass instance (e.g., [super method:5] in instance method) Previously these four cases where tangled together. Now, they have more distinct representations. Specific changes: 1) Unchanged; the object instance is represented by an Expr*. 2) Previously stored the ObjCInterfaceDecl* referring to the class receiving the message. Now stores a TypeSourceInfo* so that we know how the class was spelled. This both maintains typedef information and opens the door for more complicated C++ types (e.g., dependent types). There was an alternative, unused representation of these sends by naming the class via an IdentifierInfo *. In practice, we either had an ObjCInterfaceDecl *, from which we would get the IdentifierInfo *, or we fell into the case below... 3) Previously represented by a class message whose IdentifierInfo * referred to "super". Sema and CodeGen would use isStr("super") to determine if they had a send to super. Now represented as a "class super" send, where we have both the location of the "super" keyword and the ObjCInterfaceDecl* of the superclass we're targetting (statically). 4) Previously represented by an instance message whose receiver is a an ObjCSuperExpr, which Sema and CodeGen would check for via isa<ObjCSuperExpr>(). Now represented as an "instance super" send, where we have both the location of the "super" keyword and the ObjCInterfaceDecl* of the superclass we're targetting (statically). Note that ObjCSuperExpr only has one remaining use in the AST, which is for "super.prop" references. The new representation of ObjCMessageExpr is 2 pointers smaller than the old one, since it combines more storage. It also eliminates a leak when we loaded message-send expressions from a precompiled header. The representation also feels much cleaner to me; comments welcome! This patch attempts to maintain the same semantics we previously had with Objective-C message sends. In several places, there are massive changes that boil down to simply replacing a nested-if structure such as: if (message has a receiver expression) { // instance message if (isa<ObjCSuperExpr>(...)) { // send to super } else { // send to an object } } else { // class message if (name->isStr("super")) { // class send to super } else { // send to class } } with a switch switch (E->getReceiverKind()) { case ObjCMessageExpr::SuperInstance: ... case ObjCMessageExpr::Instance: ... case ObjCMessageExpr::SuperClass: ... case ObjCMessageExpr::Class:... } There are quite a few places (particularly in the checkers) where send-to-super is effectively ignored. I've placed FIXMEs in most of them, and attempted to address send-to-super in a reasonable way. This could use some review. llvm-svn: 101972
-
Anders Carlsson authored
llvm-svn: 101962
-
John Thompson authored
llvm-svn: 101960
-
Ted Kremenek authored
Fix USRs for @synthesize. Add more USR tests. llvm-svn: 101954
-
Ted Kremenek authored
llvm-svn: 101953
-
Anders Carlsson authored
llvm-svn: 101952
-
Fariborz Jahanian authored
It is ok to have c++-ness inside extern "C" block. Fixes pr6644. llvm-svn: 101948
-
- Apr 20, 2010
-
-
Chris Lattner authored
llvm-svn: 101943
-
Ted Kremenek authored
llvm-svn: 101941
-
Chris Lattner authored
a const_cast. llvm-svn: 101940
-
Chris Lattner authored
into ContentCache::getBuffer. This allows it to produce diagnostics on the broken #include line instead of without a location. llvm-svn: 101939
-
Fariborz Jahanian authored
objective-c methods. Fixes radar 7875968. llvm-svn: 101935
-
Chris Lattner authored
about it instead of producing tons of garbage from the lexer. It would be even better for sourcemgr to dynamically transcode (e.g. from UTF16 -> UTF8). llvm-svn: 101924
-