summaryrefslogtreecommitdiffstats
path: root/clang/lib
Commit message (Collapse)AuthorAgeFilesLines
* modern objective-c rewriter: remove 'const' fromFariborz Jahanian2012-03-211-34/+30
| | | | | | | pointer field declarations in several meta-data. // rdar://11079898 llvm-svn: 153196
* Undo previous patch as I checked more than I intended.Fariborz Jahanian2012-03-212-37/+36
| | | | llvm-svn: 153193
* modern objective-c rewriter: remove 'const' fromFariborz Jahanian2012-03-212-36/+37
| | | | | | | pointer field declarations in several meta-data. // rdar://11079898 llvm-svn: 153192
* For the annals of subtle but terrible bugs: fix a longstanding bugJohn McCall2012-03-211-5/+5
| | | | | | | | | | | | | | | | | | | | in vtable layout where virtual methods inherited from virtual bases could be assigned the same vcall adjustment slot if they shared a name and parameter signature but differed in their cv-qualification. The code was already trying to handle this case, but unfortunately used the ordinary type qualifiers (which are always empty here) instead of the method qualifiers. This seems like something that the API should discourage, but I don't know how to carry that principle out in this instance. Eliminate this function's need for an ASTContext while we're at it. This bug affects the ABI, and fixing it brings us into accord with the Itanium ABI (and GCC's implementation of it), but, obviously, technically breaks full compatibility with previous releases of Clang. Just letting you know. llvm-svn: 153168
* RewriteModernObjC.cpp: Don't expose temporary std::string with StringRef. ↵NAKAMURA Takumi2012-03-211-1/+1
| | | | | | (StringRef)getName() can be used here. llvm-svn: 153156
* Close the paren.Fariborz Jahanian2012-03-211-2/+2
| | | | | | // rdar://11076938 llvm-svn: 153151
* Update comment.Eric Christopher2012-03-201-2/+1
| | | | llvm-svn: 153149
* modern objective-c translator: insert couple of pragmas for optimization.Fariborz Jahanian2012-03-201-0/+4
| | | | | | // rdar://11079898 llvm-svn: 153145
* modern objective-c translator: add static function to initialize Fariborz Jahanian2012-03-201-3/+28
| | | | | | | the class pointer in the category structure. // rdar://11076938 llvm-svn: 153138
* More careful consideration of C++11 13.3.3.1p4. Fixes PR12257.Sebastian Redl2012-03-201-7/+19
| | | | llvm-svn: 153130
* Fix the other place where C++98 work for initializer lists was necessary.Sebastian Redl2012-03-201-2/+3
| | | | llvm-svn: 153129
* more modern objective-c meta-data stuff.Fariborz Jahanian2012-03-201-3/+17
| | | | llvm-svn: 153127
* Fix a use-after-free in thunk emission. EmitThunk may call RAUW on Init, ↵Benjamin Kramer2012-03-201-1/+1
| | | | | | | | invalidating the pointer. Fixes PR12284. The test case only triggered under asan/valgrind, but it's better than nothing. llvm-svn: 153120
* modern objective-c translator: provide meta-data initializationFariborz Jahanian2012-03-201-17/+71
| | | | | | | via functions for certain pointer initialization fields. // rdar://11076938 llvm-svn: 153117
* Debug info: Tighten up uses of plain MDNode pointers which don't survive ↵Benjamin Kramer2012-03-201-15/+13
| | | | | | | | replaceOperandWith. TrackingVH notices when it gets RAUW'd. Fixes PR12305 and PR12315. llvm-svn: 153115
* modern objective-c translator: couple of minorFariborz Jahanian2012-03-201-3/+3
| | | | | | | changes to how meta-data is declared. // rdar://11076938 llvm-svn: 153098
* objective-c modern translator: Refactor intername ivar names toFariborz Jahanian2012-03-201-21/+23
| | | | | | | one place and use it throughout. Also, change ivar name to avoid name collisions. // rdar://11079366 llvm-svn: 153093
* [avx] Define the _mm256_loadu2_xxx and _mm256_storeu2_xxx intrinsics.Chad Rosier2012-03-201-0/+67
| | | | | | | | | From the Intel Optimization Reference Manual, Section 11.6.2. When data cannot be aligned or alignment is not known, 16-byte memory accesses may provide better performance. rdar://11076953 llvm-svn: 153091
* Add missing bitcast that was breaking Objective-C++ exception typeinfo ↵David Chisnall2012-03-201-1/+2
| | | | | | (GNUstep runtime). llvm-svn: 153090
* Fix crash when querying the CFG reported when using the thread safety analysisTed Kremenek2012-03-191-1/+1
| | | | | | | on code using multi-dimensional arrays. Fix by DeLesley Hutchins, and reported in PR 12271. llvm-svn: 153067
* removed unused code in the modern objc rewriter file.Fariborz Jahanian2012-03-191-68/+0
| | | | llvm-svn: 153052
* modern objective-c translator: fix type of objc_exception_throwFariborz Jahanian2012-03-191-3/+3
| | | | | | declaration and its siblings. llvm-svn: 153043
* Fix a regression where ':' in CPLUS_INCLUDE_PATH and friends would no longer ↵Nico Weber2012-03-191-2/+2
| | | | | | | | separate paths. This regressed in r152583. Also add a test to make sure it doesn't regress again. llvm-svn: 153034
* Add the missing compatibility warning for braced initializers as default ↵Sebastian Redl2012-03-181-2/+3
| | | | | | arguments. llvm-svn: 153026
* [analyzer] Mark a failed-realloc's result as an interesting symbol between ↵Jordy Rose2012-03-181-3/+27
| | | | | | | | | | the realloc call and the null check, so we get nicer path notes. Fixes a regression introduced by the diagnostic pruning added in r152361. This is accomplished by calling markInteresting /during/ path diagnostic generation, and as such relies on deterministic ordering of BugReporterVisitors -- namely, that BugReporterVisitors are run in /reverse/ order from how they are added. (Right now that's a consequence of storing visitors in an ImmutableList, where new items are added to the front.) It's a little hacky, but it works for now. I think this is the best we can do without storing the relation between the old and new symbols, and that would be a hit whether or not there ends up being an error. llvm-svn: 153010
* Turns #import in MS Mode into an error.Aaron Ballman2012-03-181-2/+18
| | | | llvm-svn: 153009
* Use character literals for vexing initialization fixit hints.David Blaikie2012-03-181-0/+8
| | | | | | | | | | | | | | | Instead of suggesting " = 0" for "char c();", suggest " = '\0'", and similarly for other char types (wide, 16, and 32). Add tests for all these, and since this means testing such hints under C++0x, add tests for some untested C++0x hint cases in the existing code, including suggesting nullptr for pointer initialization. This sets up the initialization helper to provide better type fidelity that will be especially helpful for non-assignment cases (such as fixit-correcting NULL usage in function calls (eg: foo(char) + foo(NULL) => foo('\0') instead of the less informative foo(0))) llvm-svn: 153008
* [analyzer] Use a FoldingSet to cache simple RetainSummary instances, rather ↵Jordy Rose2012-03-181-40/+58
| | | | | | | | | | than explicitly keeping DoNothing and StopTracking summaries and nothing else. I tried to test the effects of this change on memory usage and run time, but what I saw on retain-release.m was indistinguishable from noise (debug and release builds). Even so, some caveman profiling showed 101 cache hits that we would have generated new summaries for before (i.e. not default or stop summaries), and the more code we analyze, the more memory we should save. Maybe we should have a standard project for benchmarking the retain count checker's memory and time? llvm-svn: 153007
* Replace a FIXME with a diagnostic when we can't resolve theDouglas Gregor2012-03-181-1/+2
| | | | | | nested-name-specifier for a class template declaration. Fixes PR12291. llvm-svn: 153006
* Diagnose tag and class template declarations with qualifiedDouglas Gregor2012-03-172-27/+47
| | | | | | declarator-ids that occur at class scope. Fixes PR8019. llvm-svn: 153002
* [analyzer] Unify retain-count summary generation for class and instance ↵Jordy Rose2012-03-171-53/+26
| | | | | | methods. No functionality change. llvm-svn: 153001
* Kill cocoa::deriveNamingConvention and cocoa::followsFundamentalRule. They ↵Jordy Rose2012-03-172-41/+0
| | | | | | | | are now just simple wrappers around method families, and method decls can cache method family lookups. Also, no one is using them right now. The one difference between ObjCMethodDecl::getMethodFamily and Selector::getMethodFamily is that the former will do some additional sanity checking, and since CoreFoundation types don't look like Objective-C objects, an otherwise interesting method will get a method family of OMF_None. Future clients that use method families should consider how they want to handle CF types. llvm-svn: 153000
* [analyzer] Remove duplicate work on deriving method behavior. No ↵Jordy Rose2012-03-171-83/+74
| | | | | | | | | | functionality change. The cocoa::deriveNamingConventions helper is just using method families anyway now, and the way RetainSummaryTemplate works means we're allocating an extra summary for every method with a relevant family. Also, fix RetainSummaryTemplate to do the right thing w/r/t annotating an /existing/ summary. This was probably the real cause of <rdar://problem/10824732> and the fix in r152448. llvm-svn: 152998
* modern objective-c rewriter: further improvement inFariborz Jahanian2012-03-171-29/+22
| | | | | | | | writing @synchronized statement; do not call locking expression more than once and support early exits in @synchronized's statement block (such as return). llvm-svn: 152993
* StaticAnalyzer: Fix abuse of StringRef in r152962.NAKAMURA Takumi2012-03-171-1/+1
| | | | llvm-svn: 152982
* When determining the availability of an enum constant, also considerDouglas Gregor2012-03-171-2/+11
| | | | | | | the availability of the enumeration type itself. Fixes <rdar://problem/10996386>. llvm-svn: 152977
* [analyzer] Don't claim an object was returned with +1 retain count before ↵Jordy Rose2012-03-171-4/+8
| | | | | | | | counting autoreleases. Fixes PR10376. (Also, 80-column violations.) llvm-svn: 152976
* Fix crash on invalid code. I've tried to produce a reduced test case, but ↵Ted Kremenek2012-03-171-1/+10
| | | | | | when I do the specific crash is hidden. Fixes <rdar://problem/11063594>. llvm-svn: 152968
* [analyzer] Shorten the stack hint diagnostic.Anna Zaks2012-03-162-9/+12
| | | | | | | Do not display the standard "Returning from 'foo'", when a stack hint is available. llvm-svn: 152964
* [analyzer] Create symbol-aware stack hints (building upon r152837).Anna Zaks2012-03-163-20/+142
| | | | | | | | | | | | | | | | | | The symbol-aware stack hint combines the checker-provided message with the information about how the symbol was passed to the callee: as a parameter or a return value. For malloc, the generated messages look like this : "Returning from 'foo'; released memory via 1st parameter" "Returning from 'foo'; allocated memory via 1st parameter" "Returning from 'foo'; allocated memory returned" "Returning from 'foo'; reallocation of 1st parameter failed" (We are yet to handle cases when the symbol is a field in a struct or an array element.) llvm-svn: 152962
* [analyzer] +CommentsAnna Zaks2012-03-161-5/+9
| | | | llvm-svn: 152961
* [analyzer] Add a statistic for the number of times we reach the maxAnna Zaks2012-03-161-1/+10
| | | | | | number of steps in the work list. llvm-svn: 152960
* Escape % in diagnostic message when compiling LLVM IR.Benjamin Kramer2012-03-161-1/+11
| | | | | | | % is a common character in IR so we'd crash on almost any malformed IR. The diagnostic formatter expects a formatting directive when it sees an unescaped %. llvm-svn: 152956
* sink variable into assertMatt Beaumont-Gay2012-03-161-3/+2
| | | | llvm-svn: 152955
* When "low alignment" is specified, then set the alignment of the aggregate'sBill Wendling2012-03-161-1/+3
| | | | | | | | | | store to 1. This allows code-gen to select a more appropriate alignment. If left to zero, an alignment greater than the alignment of the pointer may be selected, causing code-gen to use instructions which require an alignment greater than the pointer guarantees. <rdar://problem/11043589> llvm-svn: 152951
* Minor clean up of my last patch.Fariborz Jahanian2012-03-161-7/+5
| | | | llvm-svn: 152950
* modern objective-c translator: write @synchronized.Fariborz Jahanian2012-03-161-34/+24
| | | | | | // rdar://11063663 llvm-svn: 152949
* Suppress macro expansion of NULL in NULL warnings.David Blaikie2012-03-161-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For "int i = NULL;" we would produce: null.cpp:5:11: warning: implicit conversion of NULL constant to integer [-Wconversion] int i = NULL; ~ ^~~~ null.cpp:1:14: note: expanded from macro 'NULL' \#define NULL __null ^~~~~~ But we really shouldn't trace that macro expansion back into the header, yet we still want macro back traces for code like this: \#define FOO NULL int i = FOO; or \#define FOO int i = NULL; FOO While providing appropriate tagging at different levels of the expansion, etc. The included test case exercises these cases & does some basic validation (to ensure we don't have macro expansion notes where we shouldn't, and do where we should) - but doesn't go as far as to validate the source location/ranges used in those notes and warnings. llvm-svn: 152940
* Skip through transparent contexts when deciding where to add a friend function.Nick Lewycky2012-03-161-1/+1
| | | | | | This fixes g++.dg/parse/friend5.C. llvm-svn: 152938
* modern objective-c translator: writing @throw statement.Fariborz Jahanian2012-03-161-3/+4
| | | | llvm-svn: 152931
OpenPOWER on IntegriCloud