summaryrefslogtreecommitdiffstats
path: root/clang/lib
Commit message (Collapse)AuthorAgeFilesLines
* objc modern translator. ivar offset symbols.Fariborz Jahanian2012-02-131-2/+40
| | | | llvm-svn: 150413
* [analyzer] Malloc Checker: realloc: correct the way we are handing theAnna Zaks2012-02-131-8/+9
| | | | | | case when size is 0. llvm-svn: 150412
* Don't route explicit construction via list-initialization through the ↵Sebastian Redl2012-02-132-16/+33
| | | | | | functional cast code path. It sometimes does the wrong thing, produces horrible error messages, and is just unnecessary. llvm-svn: 150408
* Sink variable into assertMatt Beaumont-Gay2012-02-131-2/+2
| | | | llvm-svn: 150407
* objective-c translator: more rewriting of ivar typesFariborz Jahanian2012-02-131-8/+29
| | | | | | into a c-type which closely matches the objective-c type. llvm-svn: 150406
* When generating diagnostic information due to a clang failure, allow multipleChad Rosier2012-02-131-9/+10
| | | | | | | | | -arch options if the're all the same. Patch by Jeremy Huddleston. rdar://10849701 llvm-svn: 150403
* [analyzer] Malloc checker: rework realloc handling:Anna Zaks2012-02-131-34/+80
| | | | | | | | | | | | | | | | | | | 1) Support the case when realloc fails to reduce False Positives. (We essentially need to restore the state of the pointer being reallocated.) 2) Realloc behaves differently under special conditions (from pointer is null, size is 0). When detecting these cases, we should consider under-constrained states (size might or might not be 0). The old version handled this in a very hacky way. The code did not differentiate between definite and possible (no consideration for under-constrained states). Further, after processing each special case, the realloc processing function did not return but chained to the next special case processing. So you could end up in an execution in which you first see the states in which size is 0 and realloc ~ free(), followed by the states corresponding to size is not 0 followed by the evaluation of the regular realloc behavior. llvm-svn: 150402
* Split the storage of lambda information between the LambdaExpr and theDouglas Gregor2012-02-132-92/+53
| | | | | | | | | | | | CXXRecordDecl in a way that actually makes some sense: - LambdaExpr contains all of the information for initializing the lambda object, including the capture initializers and associated array index variables. - CXXRecordDecl's LambdaDefinitionData contains the captures, which are needed to understand the captured variable references in the body of the lambda. llvm-svn: 150401
* Keep track of the set of array index variables we use when weDouglas Gregor2012-02-134-4/+49
| | | | | | | synthesize a by-copy captured array in a lambda. This information will be needed by IR generation. llvm-svn: 150396
* Don't allocate unused storage for captures/capture initializers in lambda ↵Douglas Gregor2012-02-131-6/+3
| | | | | | expressions llvm-svn: 150394
* Move the storage of lambda captures and capture initializers fromDouglas Gregor2012-02-133-37/+100
| | | | | | | | LambdaExpr over to the CXXRecordDecl. This allows us to eliminate the back-link from the closure type to the LambdaExpr, which will simplify and lazify AST deserialization. llvm-svn: 150393
* Add back in the code to create forward decls using temporary mdnodes.Eric Christopher2012-02-131-13/+14
| | | | llvm-svn: 150390
* Temporarily walk back a few of my recent debug info limiting changesEric Christopher2012-02-132-106/+24
| | | | | | | | while reworking how we handle wanting to emit only parts of structures. Fixes PR11970. llvm-svn: 150388
* Update constexpr implementation to match CWG's chosen approach for core issuesRichard Smith2012-02-136-137/+83
| | | | | | | | | | | | | | | | | | | | 1358, 1360, 1452 and 1453. - Instantiations of constexpr functions are always constexpr. This removes the need for separate declaration/definition checking, which is now gone. - This makes it possible for a constexpr function to be virtual, if they are only dependently virtual. Virtual calls to such functions are not constant expressions. - Likewise, it's now possible for a literal type to have virtual base classes. A constexpr constructor for such a type cannot actually produce a constant expression, though, so add a special-case diagnostic for a constructor call to such a type rather than trying to evaluate it. - Classes with trivial default constructors (for which value initialization can produce a fully-initialized value) are considered literal types. - Classes with volatile members are not literal types. - constexpr constructors can be members of non-literal types. We do not yet use static initialization for global objects constructed in this way. llvm-svn: 150359
* Delete a simplistic helper function now that llvm::Triple can provideChandler Carruth2012-02-131-13/+3
| | | | | | this functionality. llvm-svn: 150358
* more of rewriting ivar types.Fariborz Jahanian2012-02-121-2/+6
| | | | llvm-svn: 150353
* Implement the standard decltype() semantics described in C++11Douglas Gregor2012-02-121-14/+22
| | | | | | | | [dcl.type.simple]p4, which treats all xvalues as returning T&&. We had previously implemented a pre-standard variant of decltype() that doesn't cope with, e.g., static_ast<T&&>(e) very well. llvm-svn: 150348
* Within the body of a lambda expression, decltype((x)) for anDouglas Gregor2012-02-126-118/+223
| | | | | | | | | | | | | | | | id-expression 'x' will compute the type based on the assumption that 'x' will be captured, even if it isn't captured, per C++11 [expr.prim.lambda]p18. There are two related refactors that go into implementing this: 1) Split out the check that determines whether we should capture a particular variable reference, along with the computation of the type of the field, from the actual act of capturing the variable. 2) Always compute the result of decltype() within Sema, rather than AST, because the decltype() computation is now context-sensitive. llvm-svn: 150347
* Proper initializer list support for new expressions and type construct ↵Sebastian Redl2012-02-123-41/+83
| | | | | | expressions. Array new still missing. llvm-svn: 150346
* Lambdas have a deleted default constructor and a deleted copyDouglas Gregor2012-02-123-7/+21
| | | | | | assignment operator, per C++ [expr.prim.lambda]p19. Make it so. llvm-svn: 150345
* Change the way we store initialization kinds so that all direct inits can ↵Sebastian Redl2012-02-124-31/+49
| | | | | | distinguish between list and parens form. This allows us to correctly diagnose the last test cases from litb. llvm-svn: 150343
* Employ DirectList initialized entities to properly sort through some ↵Sebastian Redl2012-02-122-15/+27
| | | | | | initialization edge cases. llvm-svn: 150342
* Fix the rewriter that broke with r149987.Argyrios Kyrtzidis2012-02-122-0/+6
| | | | | | | | | | | | | r149987 changed the way parsing happens inside an @implementation; it aggregates the declarations inside and reports them together as a DeclGroup. This had the side effect that function declarations were reported together with their definition, while the rewriter expected for function declarations to be reported immediately to the consumer and thus not have a body. Fix this by having the rewriter actually check with isThisDeclarationADefinition() to make sure the body comes from the current decl before rewriting it. llvm-svn: 150325
* Represent C++ direct initializers as ParenListExprs before semantic analysisSebastian Redl2012-02-1118-540/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | instead of having a special-purpose function. - ActOnCXXDirectInitializer, which was mostly duplication of AddInitializerToDecl (leading e.g. to PR10620, which Eli fixed a few days ago), is dropped completely. - MultiInitializer, which was an ugly hack I added, is dropped again. - We now have the infrastructure in place to distinguish between int x = {1}; int x({1}); int x{1}; -- VarDecl now has getInitStyle(), which indicates which of the above was used. -- CXXConstructExpr now has a flag to indicate that it represents list- initialization, although this is not yet used. - InstantiateInitializer was renamed to SubstInitializer and simplified. - ActOnParenOrParenListExpr has been replaced by ActOnParenListExpr, which always produces a ParenListExpr. Placed that so far failed to convert that back to a ParenExpr containing comma operators have been fixed. I'm pretty sure I could have made a crashing test case before this. The end result is a (I hope) considerably cleaner design of initializers. More importantly, the fact that I can now distinguish between the various initialization kinds means that I can get the tricky generalized initializer test cases Johannes Schaub supplied to work. (This is not yet done.) This commit passed self-host, with the resulting compiler passing the tests. I hope it doesn't break more complicated code. It's a pretty big change, but one that I feel is necessary. llvm-svn: 150318
* Drive-by fix of incorrect diagnostic, and a test case for said diagnostic. ↵Sebastian Redl2012-02-111-2/+2
| | | | | | The double error is unfortunate, but I really don't see an alternative whose effort is worth it. llvm-svn: 150317
* Fix parsing new expressions using init lists. Probably still do the wrong ↵Sebastian Redl2012-02-112-6/+86
| | | | | | | | thing in cases involving array new. Show that many cases using initializer list constructors work, in that they parse and pass semantic analysis. llvm-svn: 150316
* [analyzer] Malloc Checker: reduce false negatives rate by assuming thatAnna Zaks2012-02-111-6/+28
| | | | | | | a pointer cannot escape through calls to system functions. Also, stop after reporting the first use-after-free. llvm-svn: 150315
* [analyzer] Malloc Checker: Report a leak when we are returning freedAnna Zaks2012-02-111-0/+6
| | | | | | | | | memory. (As per one test case, the existing checker thought that this could cause a lot of false positives - not sure if that's valid, to be verified.) llvm-svn: 150313
* [analyzer] Malloc checker: Leak bugs should be suppressed by sinks.Anna Zaks2012-02-111-18/+28
| | | | | | | Resolves a common false positive, where we were reporting a leak inside asserts llvm-svn: 150312
* [analyzer] MallocChecker: refactor/improve the symbol escape logic.Anna Zaks2012-02-111-71/+103
| | | | | | We use the same logic here as the RetainRelease checker. llvm-svn: 150311
* objective-c translator. more modern abi stuff, focusing on ivar relatedFariborz Jahanian2012-02-111-246/+33
| | | | | | meta-data. llvm-svn: 150310
* Implement core issue 5: a temporary created for copy-initialization has aRichard Smith2012-02-111-4/+6
| | | | | | | cv-unqualified type. This is essential in order to allow move-only objects of const-qualified types to be copy-initialized via a converting constructor. llvm-svn: 150309
* Make sure to try instantiating a templated type which is used in an _AtomicRichard Smith2012-02-111-5/+7
| | | | | | before complaining that it's incomplete. llvm-svn: 150308
* [analyzer] New checker for assignment of non-0/1 values to Boolean variables.Ryan Govostes2012-02-113-0/+162
| | | | llvm-svn: 150306
* Implement warning for non-wide string literals with an unexpected encoding. ↵Eli Friedman2012-02-111-15/+40
| | | | | | Downgrade error for non-wide character literals with an unexpected encoding to a warning for compatibility with gcc and older versions of clang. <rdar://problem/10837678>. llvm-svn: 150295
* Begin refactoring to use the newly added triple predicates forChandler Carruth2012-02-112-12/+4
| | | | | | | simplicity. Also addresses a FIXME, although not one that could be observed. llvm-svn: 150294
* Basic support for referring to captured variables from lambdas. Some simple ↵Eli Friedman2012-02-116-11/+42
| | | | | | examples seem to work. Tests coming up soon. llvm-svn: 150293
* Make sure Sema creates a field for 'this' captures. (Doug, please ↵Eli Friedman2012-02-111-1/+15
| | | | | | double-check that this is correct.) llvm-svn: 150292
* For class template implicit instantiation, also update its location to pointArgyrios Kyrtzidis2012-02-111-0/+1
| | | | | | | | | | | | | | | | | | to the pattern template that it came from, otherwise we had this situation: template <typename T1, typename T2> struct S { }; template <typename T> struct S<T, int> { }; void f() { S<int, int> s; // location of declaration "S<int, int>" was of "S<T1, T2>" not "S<T, int>" } llvm-svn: 150290
* const-qualify CXXRecordDecl::getCaptureFields.Eli Friedman2012-02-111-1/+1
| | | | llvm-svn: 150284
* Implement C++11 [expr.lambda.prim]p13, which prohibits lambdas inDouglas Gregor2012-02-101-0/+12
| | | | | | default arguments if in fact those lambdas capture any entity. llvm-svn: 150282
* objc translator: more modern metadata stuff.Fariborz Jahanian2012-02-101-105/+33
| | | | llvm-svn: 150281
* Set UserLabelPrefix and MCountName correctly for DragonFly BSD. Patch by ↵Eli Friedman2012-02-101-1/+12
| | | | | | | | Sascha Wildner. Setting UserLabelPrefix correctly fixes PR11949. llvm-svn: 150280
* Support all null pointer literals in format strings.David Blaikie2012-02-101-8/+7
| | | | llvm-svn: 150276
* objctive-c translator: modern metadata for ivars. wip.Fariborz Jahanian2012-02-101-28/+78
| | | | llvm-svn: 150275
* Have the driver pass CPU and target feature information to cc1as.Jim Grosbach2012-02-102-0/+62
| | | | | | | | | | When creating the MCSubtargetInfo, the assembler driver uses the CPU and feature string to construct a more accurate model of what instructions are and are not legal. rdar://10840476 llvm-svn: 150273
* [libclang] Indexing API: Fully index implict template instantiations.Argyrios Kyrtzidis2012-02-102-1/+10
| | | | llvm-svn: 150267
* Add ArrayRef goodness in MultiplexASTMutationListener.Argyrios Kyrtzidis2012-02-101-3/+3
| | | | llvm-svn: 150266
* Update MultiplexASTMutationListener with the missing methods from ↵Argyrios Kyrtzidis2012-02-101-0/+18
| | | | | | ASTMutationListener. llvm-svn: 150265
* Enhance checking for null format string literal to take into account __null. ↵Ted Kremenek2012-02-101-0/+1
| | | | | | Fixes <rdar://problem/8269537>. llvm-svn: 150260
OpenPOWER on IntegriCloud