summaryrefslogtreecommitdiffstats
path: root/clang/lib/Lex/PTHLexer.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2008-12-23 00:26:44 +0000
committerDouglas Gregor <dgregor@apple.com>2008-12-23 00:26:44 +0000
commit55297ac4991d0f75b44c4bb6a5dde48076ff827f (patch)
treea41cabf1becbd713a40aa081f8d33b06a5d704b4 /clang/lib/Lex/PTHLexer.cpp
parentd72358cba8f70912b05f210db5184332479ebc1a (diff)
downloadbcm5719-llvm-55297ac4991d0f75b44c4bb6a5dde48076ff827f.tar.gz
bcm5719-llvm-55297ac4991d0f75b44c4bb6a5dde48076ff827f.zip
Don't explicitly represent OverloadedFunctionDecls within
DeclContext. Instead, just keep the list of currently-active declarations and only build the OverloadedFunctionDecl when we absolutely need it. This is a half-step toward eliminating the need to explicitly build OverloadedFunctionDecls that store sets of overloaded functions. This was suggested by Argiris a while back, and it's a good thing for several reasons: first, it eliminates the messy logic that currently tries to keep the OverloadedFunctionDecl in sync with the declarations that are being added. Second, it will (eventually) eliminate the need to allocate memory for overload sets, which could help performance. Finally, it helps set us up for when name lookup can return multiple (possibly ambiguous) results, as can happen with lookup of class members in C++. Next steps: make the IdentifierResolver store overloads as separate entries in its list rather than replacing them with an OverloadedFunctionDecl now, then see how far we can go toward eliminating OverloadedFunctionDecl entirely. llvm-svn: 61357
Diffstat (limited to 'clang/lib/Lex/PTHLexer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud