| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | -Warc-repeated-use-of-weak: fix a use-of-uninitialized and add a test case. | Jordan Rose | 2012-10-11 | 1 | -1/+1 |
| | | | | | | | Fix-up for r165718, should get the buildbots back online. llvm-svn: 165723 | ||||
| * | -Warc-repeated-use-of-weak: Check messages to property accessors as well. | Jordan Rose | 2012-10-11 | 1 | -3/+29 |
| | | | | | | | | | | | | | | | | | | | | Previously, [foo weakProp] was not being treated the same as foo.weakProp. Now, for every explicit message send, we check if it's a property access, and if so, if the property is weak. Then for every assignment of a message, we have to do the same thing again. This is a potentially expensive increase because determining whether a method is a property accessor requires searching through the methods it overrides. However, without it -Warc-repeated-use-of-weak will miss cases from people who prefer not to use dot syntax. If this turns out to be too expensive, we can try caching the result somewhere, or even lose precision by not checking superclass methods. The warning is off-by-default, though. <rdar://problem/12407765> llvm-svn: 165718 | ||||
| * | -Warc-repeated-use-of-weak: look through explicit casts on assigned values. | Jordan Rose | 2012-10-10 | 1 | -1/+1 |
| | | | | | | | | Reading from a weak property, casting the result, and assigning to a strong pointer should still be considered safe. llvm-svn: 165629 | ||||
| * | Move isObjCSelf into Expr. | Anna Zaks | 2012-10-01 | 1 | -20/+2 |
| | | | | | llvm-svn: 164966 | ||||
| * | Pull ScopeInfo implementation into its own file. | Jordan Rose | 2012-09-28 | 1 | -0/+181 |
| The infrastructure for -Warc-repeated-use-of-weak got a little too heavy to leave sitting at the top of Sema.cpp. No functionality change. llvm-svn: 164856 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|