tree 0495705ef5f494d3dd5e65439c3c89bd13b5f84f
parent 685d10462b875f8c056d27488c0a1b4e13ef680f
author Argyrios Kyrtzidis <akyrtzi@gmail.com> 1366157348 +0000
committer Argyrios Kyrtzidis <akyrtzi@gmail.com> 1366157348 +0000

Use the extra info in global method pool to speed up looking for ObjC overridden methods.

When we are in a implementation, we check the global method pool whether there were category
methods with the same selector. If there were none (common case) we don't need to do lookups for
overridden methods again.

Note that for an interface method (if we don't encounter its implementation), it is considered that
it overrides methods that were declared before it, not for category methods introduced after it.

This is tradeoff in favor of performance, since it is expensive to do lookups in case there was a
category, and moving the global method pool to ASTContext (so we can check it) would increase complexity.

rdar://13508196

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@179654 91177308-0d34-0410-b5e6-96231b3b80d8