Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
1 result
Search by author
  • Any Author
0 authors
  1. Dec 04, 2012
  3. Nov 28, 2012
  5. Nov 14, 2012
    • John McCall's avatar
      Accept and pass arguments to __unknown_anytype in argument · b8a8de31
      John McCall authored 
      positions of Objective-C methods.

It is possible to recover a lot of type information about
Objective-C methods from the reflective metadata for their
implementations.  This information is not rich when it
comes to struct types, however, and it is not possible to
produce a type in the debugger's round-tripped AST which
will really do anything useful during type-checking.
Therefore we allow __unknown_anytype in these positions,
which essentially disables type-checking for that argument.
We infer the parameter type to be the unqualified type of
the argument expression unless that expression is an
explicit cast, in which case it becomes the type-as-written
of that cast.

rdar://problem/12565338

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@167896 91177308-0d34-0410-b5e6-96231b3b80d8
      b8a8de31
  7. Oct 19, 2012
    • Jordan Rose's avatar
      Allow objc_requires_super to be used to check class methods as well. · 535a5d00
      Jordan Rose authored 
      Also, unify ObjCShouldCallSuperDealloc and ObjCShouldCallSuperFinalize.
The two have identical behavior and will never be active at the same time.

There's one last simplification now, which is that if we see a call to
[super foo] and we are currently in a method named 'foo', we will
/unconditionally/ clear the ObjCShouldCallSuper flag, rather than check
first to see if we're in a method where calling super is required. There's
no reason to pay the extra lookup price here.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@166285 91177308-0d34-0410-b5e6-96231b3b80d8
      535a5d00
  9. Oct 11, 2012
    • Jordan Rose's avatar
      -Warc-repeated-use-of-weak: Check messages to property accessors as well. · 7fffce78
      Jordan Rose authored 
      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>

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@165718 91177308-0d34-0410-b5e6-96231b3b80d8
      7fffce78
  11. Oct 10, 2012
  13. Sep 29, 2012
  15. Sep 08, 2012
  17. Aug 31, 2012
  19. Aug 24, 2012
  21. Aug 23, 2012
  23. Aug 01, 2012
  25. Jul 31, 2012
  27. Jul 28, 2012
  29. Jul 27, 2012
  31. Jun 28, 2012
  33. Jun 23, 2012
  35. Jun 22, 2012
    • James Dennett's avatar
      Documentation cleanup: · efce31f5
      James Dennett authored 
      * Primarily fixed \param commands with names not matching any actual
  parameters of the documented functions.  In many cases this consists
  just of fixing up the parameter name in the \param to match the code,
  in some it means deleting obsolete documentation and occasionally it
  means documenting the parameter that has replaced the older one that
  was documented, which sometimes means some simple reverse-engineering
  of the docs from the implementation;
* Fixed \param ParamName [out] to the correct format with [out] before
  the parameter name;
* Fixed some \brief summaries.


git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@158980 91177308-0d34-0410-b5e6-96231b3b80d8
      efce31f5
  37. Jun 20, 2012
    • John McCall's avatar
      Restructure how the driver communicates information about the · 260611a3
      John McCall authored 
      target Objective-C runtime down to the frontend:  break this
down into a single target runtime kind and version, and compute
all the relevant information from that.  This makes it
relatively painless to add support for new runtimes to the
compiler.  Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z,
available at the driver level as a better and more general
alternative to -fgnu-runtime and -fnext-runtime.  This new
concept of an Objective-C runtime also encompasses what we
were previously separating out as the "Objective-C ABI", so
fragile vs. non-fragile runtimes are now really modelled as
different kinds of runtime, paving the way for better overall
differentiation.

As a sort of special case, continue to accept the -cc1 flag
-fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak.

I won't go so far as to say "no functionality change", even
ignoring the new driver flag, but subtle changes in driver
semantics are almost certainly not intended.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@158793 91177308-0d34-0410-b5e6-96231b3b80d8
      260611a3
  39. Jun 07, 2012
  41. Jun 04, 2012
  43. Jun 01, 2012
  45. May 30, 2012
  47. May 25, 2012
  49. May 24, 2012
  51. May 19, 2012
  53. May 16, 2012
  55. May 15, 2012
  57. May 12, 2012