summaryrefslogtreecommitdiffstats
path: root/clang/test
Commit message (Collapse)AuthorAgeFilesLines
* PR9023: A template template parameter whose template parameter list contains anRichard Smith2012-09-073-0/+161
| | | | | | | | | | | | | unexpanded parameter pack is a pack expansion. Thus, as with a non-type template parameter which is a pack expansion, it needs to be expanded early into a fixed list of template parameters. Since the expanded list of template parameters is not itself a parameter pack, it is permitted to appear before the end of the template parameter list, so also remove that restriction (for both template template parameter pack expansions and non-type template parameter pack expansions). llvm-svn: 163369
* [analyzer] Fail gracefully when the dynamic type is outside the hierarchy.Jordan Rose2012-09-071-0/+32
| | | | | | | | | | | | | | | | | | | With some particularly evil casts, we can get an object whose dynamic type is not actually a subclass of its static type. In this case, we won't even find the statically-resolved method as a devirtualization candidate. Rather than assert that this situation cannot occur, we now simply check that the dynamic type is not an ancestor or descendent of the static type, and leave it at that. This error actually occurred analyzing LLVM: CallEventManager uses a BumpPtrAllocator to allocate a concrete subclass of CallEvent (FunctionCall), but then casts it to the actual subclass requested (such as ObjCMethodCall) to perform the constructor. Yet another crash in PR13763. llvm-svn: 163367
* Teach RetainCountChecker that CFPlugInInstanceCreate does notTed Kremenek2012-09-061-0/+12
| | | | | | | | return a CF object at all. Fixes <rdar://problem/9566345> llvm-svn: 163362
* [analyzer] Don't crash if we cache out while evaluating an ObjC message.Jordan Rose2012-09-061-0/+62
| | | | | | | | | | | | | | | | A bizarre series of coincidences led us to generate a previously-seen node in the middle of processing an Objective-C message, where we assume the receiver is non-nil. We were assuming that such an assumption would never "cache out" like this, and blithely went on using a null ExplodedNode as the predecessor for the next step in evaluation. Although the test case committed here is complicated, this could in theory happen in other ways as well, so the correct fix is just to test if the non-nil assumption results in an ExplodedNode we've seen before. <rdar://problem/12243648> llvm-svn: 163361
* Refine diagnostics for leaks reported when returning an objectTed Kremenek2012-09-061-0/+9
| | | | | | | | via function/method with [CF,NS]_RETURNS_NOT_RETAINED. Fixes <rdar://problem/11379000>. llvm-svn: 163355
* Tweak DeadStoresChecker to not warn about dead stores to variables thatTed Kremenek2012-09-061-0/+17
| | | | | | | | | are used in EH code. Right now the CFG doesn't support exceptions well, so we need this hack to avoid bogus dead store warnings. Fixes <rdar://problem/12147586> llvm-svn: 163353
* Clarified diagnostics for range-based for loops with invalid rangesSam Panzer2012-09-061-3/+16
| | | | llvm-svn: 163350
* [analyzer] Don't attempt to devirtualize calls to base class destructors.Jordan Rose2012-09-061-0/+30
| | | | | | | | | | | | | | | | | | | CXXDestructorCall now has a flag for when it is a base destructor call. Other kinds of destructor calls (locals, fields, temporaries, and 'delete') all behave as "whole-object" destructors and do not behave differently from one another (specifically, in these cases we /should/ try to devirtualize a call to a virtual destructor). This was causing crashes in both our internal buildbot, the crash still being tracked in PR13765, and some of the crashes being tracked in PR13763, due to a assertion failure. (The behavior under -Asserts happened to be correct anyway.) Adding this knowledge also allows our DynamicTypePropagation checker to do a bit less work; the special rules about virtual method calls during a destructor only require extra handling during base destructors. llvm-svn: 163348
* [ms-inline asm] Output empty asm statements for the directives we don'tChad Rosier2012-09-061-0/+9
| | | | | | | handle. Otherwise, the AsmParser will explode if we try to generate an object files. llvm-svn: 163345
* [ms-inline asm] The IR representation of inline assembly enumerates the inputChad Rosier2012-09-061-1/+1
| | | | | | | and output expressions much like that in GNU-style inline assembly. Output expressions are first. Do this for MS-style inline asms. llvm-svn: 163342
* refactoring + objective-C specific test for my last patch.Fariborz Jahanian2012-09-061-1/+15
| | | | | | // rdar://12233989 llvm-svn: 163338
* Don't try to check override control for invalid member functions. Fixes a ↵Richard Smith2012-09-061-0/+5
| | | | | | crash in a corner case. Patch by Olivier Goffart! llvm-svn: 163337
* Use custom ABIInfo for le32/PNaCl argument codegenDerek Schuff2012-09-062-0/+102
| | | | | | | | | This patch uses a new ABIInfo implementation specific to the le32 target, rather than falling back to DefaultABIInfo. Its behavior is basically the same, but it also allows the regparm argument attribute. It also includes basic tests for argument codegen and attributes. llvm-svn: 163333
* Fixing the return type information for objc_sync_enter and objc_sync_exit. ↵Aaron Ballman2012-09-062-6/+6
| | | | | | Patch thanks to Joe Ranieri! llvm-svn: 163330
* c: make __attribute__((unused)) transitive.Fariborz Jahanian2012-09-061-1/+13
| | | | | | | Don't warn if annotated decl is used inside another unused. // rdar://12233989 llvm-svn: 163329
* Tighten up regexps some more.Jakob Stoklund Olesen2012-09-061-4/+4
| | | | | | | These tests were failing for me because the .* was greedily matching up to the /libexec/ld-elf.so.1" later on the same line. llvm-svn: 163328
* PR13775: When checking for a tag type being shadowed by some other declaration,Richard Smith2012-09-061-0/+14
| | | | | | don't trample over the caller's LookupResult in the case where the check fails. llvm-svn: 163281
* [analyzer] Enhance the member expr tracking to account for references.Anna Zaks2012-09-051-0/+16
| | | | | | As per Jordan's suggestion. (Came out of code review for r163261.) llvm-svn: 163269
* Format strings: suggest casts for NS(U)Integer and [SU]Int32 on Darwin.Jordan Rose2012-09-051-0/+181
| | | | | | | | | | | | | | | These types are defined differently on 32-bit and 64-bit platforms, and trying to offer a fixit for one platform would only mess up the format string for the other. The Apple-recommended solution is to cast to a type that is known to be large enough and always use that to print the value. This should only have an impact on compile time if the format string is incorrect; in cases where the format string matches the definition on the current platform, no warning will be emitted. <rdar://problem/9135072&12164284> llvm-svn: 163266
* [analyzer] Always include destructors in the analysis CFG.Jordan Rose2012-09-055-4/+29
| | | | | | | | | | | | | | | | | | | | | While destructors will continue to not be inlined (unless the analyzer config option 'c++-inlining' is set to 'destructors'), leaving them out of the CFG is an incomplete model of the behavior of an object, and can cause false positive warnings (like PR13751, now working). Destructors for temporaries are still not on by default, since (a) we haven't actually checked this code to be sure it's fully correct (in particular, we probably need to be very careful with regard to lifetime-extension when a temporary is bound to a reference, C++11 [class.temporary]p5), and (b) ExprEngine doesn't actually do anything when it sees a temporary destructor in the CFG -- not even invalidate the object region. To enable temporary destructors, set the 'cfg-temporary-dtors' analyzer config option to '1'. The old -cfg-add-implicit-dtors cc1 option, which controlled all implicit destructors, has been removed. llvm-svn: 163264
* [analyzer] Fix a crash PR13762.Anna Zaks2012-09-051-0/+6
| | | | llvm-svn: 163262
* [analyzer] NullOrUndef diagnostics: track symbols binded to regions.Anna Zaks2012-09-051-0/+354
| | | | | | | | | If a region is binded to a symbolic value, we should track the symbol. (The code I changed was not previously exercised by the regression tests.) llvm-svn: 163261
* Add test missed in previous commit.Eric Christopher2012-09-051-0/+56
| | | | llvm-svn: 163253
* Try to fix the windows bots.Eric Christopher2012-09-051-4/+4
| | | | llvm-svn: 163252
* Apply some driver improvements for freebsd-*-mips*.Eric Christopher2012-09-051-1/+29
| | | | | | Patch by Brooks Davis. llvm-svn: 163249
* Thread-safety analysis: bugfix for case where a trylock occurs in anDeLesley Hutchins2012-09-051-0/+27
| | | | | | expression involving temporaries. llvm-svn: 163237
* objective-c++11: c++11 does not change pod-ness whenFariborz Jahanian2012-09-051-0/+12
| | | | | | | | type is an unqualified objc pointer in arc. Treat it just as being treated in c++98. This fixes a bogus vararg warning with -std=c++11. //rdar://12229679 llvm-svn: 163236
* Update for r163231.Chad Rosier2012-09-051-16/+16
| | | | llvm-svn: 163232
* Added missing test.Abramo Bagnara2012-09-051-0/+2
| | | | llvm-svn: 163226
* c error recovery. treat an invalid redeclarationFariborz Jahanian2012-09-051-0/+9
| | | | | | | | of a c-function for what it is. Otherwise, this func is treated as an overloadable c-function resulting in a crash much later. // rdar://11743706 llvm-svn: 163224
* [analyzer] Fix bad test from r163220.Jordan Rose2012-09-051-0/+6
| | | | | | Add a FIXME to the test while I track down the real problem. llvm-svn: 163222
* [analyzer] Be more forgiving about calling methods on struct rvalues.Jordan Rose2012-09-052-9/+94
| | | | | | | | | | | | | | | | | | | | The problem is that the value of 'this' in a C++ member function call should always be a region (or NULL). However, if the object is an rvalue, it has no associated region (only a conjured symbol or LazyCompoundVal). For now, we handle this in two ways: 1) Actually respect MaterializeTemporaryExpr. Before, it was relying on CXXConstructExpr to create temporary regions for all struct values. Now it just does the right thing: if the value is not in a temporary region, create one. 2) Have CallEvent recognize the case where its 'this' pointer is a non-region, and just return UnknownVal to keep from confusing clients. The long-term problem is being tracked internally in <rdar://problem/12137950>, but this makes many test cases pass. llvm-svn: 163220
* Revert "[analyzer] Treat all struct values as regions (even rvalues)."Jordan Rose2012-09-052-92/+9
| | | | | | | | | | | | | | This turned out to have many implications, but what eventually seemed to make it unworkable was the fact that we can get struct values (as LazyCompoundVals) from other places besides return-by-value function calls; that is, we weren't actually able to "treat all struct values as regions" consistently across the entire analyzer core. Hopefully we'll be able to come up with an alternate solution soon. This reverts r163066 / 02df4f0aef142f00d4637cd851e54da2a123ca8e. llvm-svn: 163218
* [ms-inline asm] Update test case for r163181.Chad Rosier2012-09-051-16/+16
| | | | llvm-svn: 163182
* [ms-inline asm] Remove the Inline Asm Non-Standard Dialect attribute. ThisChad Rosier2012-09-041-16/+16
| | | | | | | implementation does not co-exist well with how the sideeffect and alignstack attributes are handled. llvm-svn: 163173
* [analyzer] Don't use makeIntVal to create a floating-point value.Jordan Rose2012-09-041-0/+8
| | | | | | | | | | SimpleSValBuilder processes a couple trivial identities, including 'x - x' and 'x ^ x' (both 0). However, the former could appear with arguments of floating-point type, and we weren't checking for that. This started triggering an assert with r163069, which checks that a constant value is actually going to be used as an integer or pointer. llvm-svn: 163159
* Revert r163083 per chandlerc's request.Joao Matos2012-09-041-6/+0
| | | | llvm-svn: 163149
* Revert r163078 per chandlerc's request.Joao Matos2012-09-041-7/+5
| | | | llvm-svn: 163145
* [ms-inline asm] The MCInstrDesc only tracks register definitions. For now,Chad Rosier2012-09-041-2/+1
| | | | | | | assume that if the 1st operands is an expression and the instruction mayStore, then it is a memory definition. llvm-svn: 163144
* test/Driver/android-standalone.cpp: Fix test failure on Windowns, again.NAKAMURA Takumi2012-09-031-1/+1
| | | | llvm-svn: 163114
* Fix test failure on Windowns.Evgeniy Stepanov2012-09-031-1/+1
| | | | llvm-svn: 163112
* Follow-up on r163110 - forgot to commit some new tests...Timur Iskhodzhanov2012-09-031-0/+78
| | | | llvm-svn: 163111
* Fix PR13444 - wrong mangling of "const char * const *" and friends with ↵Timur Iskhodzhanov2012-09-032-9/+29
| | | | | | "-cxx-abi microsoft" llvm-svn: 163110
* Android standalone toolchain support.Evgeniy Stepanov2012-09-0316-8/+25
| | | | | | | | This change adds detection of C++ headers and libraries paths when building with the standalone toolchain from Android NDK. They are in a slightly unusual place. llvm-svn: 163109
* Rename ANDROIDEABI to Android.Logan Chien2012-09-021-0/+14
| | | | | | | | | | | | | Most of the code guarded with ANDROIDEABI are not ARM-specific, and having no relation with arm-eabi. Thus, it will be more natural to call this environment "Android" instead of "ANDROIDEABI". Note: We are not using ANDROID because several projects are using "-DANDROID" as the conditional compilation flag. llvm-svn: 163088
* Implemented parsing and AST support for the MS __leave exception statement. ↵Joao Matos2012-09-021-0/+6
| | | | | | Also a minor fix to __except printing in StmtPrinter.cpp. Thanks to Aaron Ballman for review. llvm-svn: 163083
* Added a diagnostic for mismatched MS inheritance attributes. Also fixed the ↵Joao Matos2012-09-021-5/+7
| | | | | | incomplete type member pointer size calculation under the MS ABI. llvm-svn: 163078
* [libclang] Fix indexing type alias declarations. rdar://11878406Argyrios Kyrtzidis2012-09-011-0/+6
| | | | llvm-svn: 163072
* [libclang] The annotation of tokens operation visits statement nodes ↵Argyrios Kyrtzidis2012-09-011-0/+95
| | | | | | | | | | | | | | code-recursively. This can blow the stack with extremely deep hierarchies. Switch it to data-recursive. This is implemented by introducing a post-children visitation callback that the CursorVisitor is calling after child nodes of a cursor have been visited. This is used by the annotate-tokens visitor to do extra work at that point. rdar://11979525. llvm-svn: 163071
* [analyzer] Treat all struct values as regions (even rvalues).Jordan Rose2012-09-012-9/+92
| | | | | | | | | | | | | | | | | This allows us to correctly symbolicate the fields of structs returned by value, as well as get the proper 'this' value for when methods are called on structs returned by value. This does require a moderately ugly hack in the StoreManager: if we assign a "struct value" to a struct region, that now appears as a Loc value being bound to a region of struct type. We handle this by simply "dereferencing" the struct value region, which should create a LazyCompoundVal. This should fix recent crashes analyzing LLVM and on our internal buildbot. <rdar://problem/12137950> llvm-svn: 163066
OpenPOWER on IntegriCloud