[cfe-dev] Missing edges in analysis call graph
Anna Zaks
ganna at apple.com
Mon Dec 15 16:15:00 PST 2014
Hi Daniel,
This one prints "Function: eee calls:" twice. I think the check should be done inside getOrInsertNode (instead of VisitFunctionDecl). What do you think? If this looks good, I am going to go ahead and commit the patch. (I'll also replace CHECK with CHECK-NEXT.)
CallGraphNode *CallGraph::getOrInsertNode(Decl *F) {
if (F && !isa<ObjCMethodDecl>(F))
F = F->getCanonicalDecl();
Anna.
> On Dec 4, 2014, at 2:20 AM, Daniel DeFreez <dcdefreez at ucdavis.edu> wrote:
>
> OK, here's another go at it. This fixes the two test cases discussed, and doesn't break anything else that I can see.
>
> Because callees do not always match the canonical declaration, I swap FunctionDecls for their canonical counterparts when they are visited.
>
> This differs from what we discussed by not using the canonical declaration for ObjCMethodDecls. This is because hasBody and getBody work differently for ObjCMethodDecls than FunctionDecls. Using the canonical declaration breaks the call graph. There isn't a problem with the call graph created for ObjCMethodDecls, so I have left them alone. Also for ObjCMethodDecls, isThisDeclarationADefinition is just { return hasBody(); }, so that includeInGraph check is redundant.
>
> Thoughts?
>
> ---
> include/clang/Analysis/CallGraph.h | 1 +
> lib/Analysis/CallGraph.cpp | 10 ++--------
> test/Analysis/debug-CallGraph.c | 14 +++++++++++++-
> 3 files changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/include/clang/Analysis/CallGraph.h b/include/clang/Analysis/CallGraph.h
> index eda22a5..49aad7a 100644
> --- a/include/clang/Analysis/CallGraph.h
> +++ b/include/clang/Analysis/CallGraph.h
> @@ -95,6 +95,7 @@ public:
> /// Part of recursive declaration visitation. We recursively visit all the
> /// declarations to collect the root functions.
> bool VisitFunctionDecl(FunctionDecl *FD) {
> + FD = FD->getCanonicalDecl();
> // We skip function template definitions, as their semantics is
> // only determined when they are instantiated.
> if (includeInGraph(FD)) {
> diff --git a/lib/Analysis/CallGraph.cpp b/lib/Analysis/CallGraph.cpp
> index f41a96d..5ea2dc3 100644
> --- a/lib/Analysis/CallGraph.cpp
> +++ b/lib/Analysis/CallGraph.cpp
> @@ -110,14 +110,13 @@ CallGraph::~CallGraph() {
>
> bool CallGraph::includeInGraph(const Decl *D) {
> assert(D);
> - if (!D->getBody())
> + if (!D->hasBody())
> return false;
>
> if (const FunctionDecl *FD = dyn_cast<FunctionDecl>(D)) {
> // We skip function template definitions, as their semantics is
> // only determined when they are instantiated.
> - if (!FD->isThisDeclarationADefinition() ||
> - FD->isDependentContext())
> + if (FD->isDependentContext())
> return false;
>
> IdentifierInfo *II = FD->getIdentifier();
> @@ -125,11 +124,6 @@ bool CallGraph::includeInGraph(const Decl *D) {
> return false;
> }
>
> - if (const ObjCMethodDecl *ID = dyn_cast<ObjCMethodDecl>(D)) {
> - if (!ID->isThisDeclarationADefinition())
> - return false;
> - }
> -
> return true;
> }
>
> diff --git a/test/Analysis/debug-CallGraph.c b/test/Analysis/debug-CallGraph.c
> index 4523c78..ea7ea70 100644
> --- a/test/Analysis/debug-CallGraph.c
> +++ b/test/Analysis/debug-CallGraph.c
> @@ -24,8 +24,20 @@ void bbb(int y) {
> }();
> }
>
> +void ccc();
> +void ddd() { ccc(); }
> +void ccc() {}
> +
> +void eee();
> +void eee() {}
> +void fff() { eee(); }
> +
> // CHECK:--- Call graph Dump ---
> -// CHECK: Function: < root > calls: mmm foo aaa < > bbb
> +// CHECK: Function: < root > calls: mmm foo aaa < > bbb ccc ddd eee fff
> +// CHECK: {{Function: fff calls: eee $}}
> +// CHECK: {{Function: eee calls: $}}
> +// CHECK: {{Function: ddd calls: ccc $}}
> +// CHECK: {{Function: ccc calls: $}}
> // CHECK: Function: bbb calls: < >
> // CHECK: Function: < > calls: foo
> // CHECK: Function: aaa calls: foo
> --
> 1.9.1
>
>
>
>
> On Sat, Nov 22, 2014 at 2:23 AM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote:
>
>> On Nov 21, 2014, at 5:21 PM, Daniel DeFreez <dcdefreez at ucdavis.edu <mailto:dcdefreez at ucdavis.edu>> wrote:
>>
>>
>> On Sat, Nov 22, 2014 at 2:11 AM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote:
>>
>>> On Nov 21, 2014, at 5:01 PM, Daniel DeFreez <dcdefreez at ucdavis.edu <mailto:dcdefreez at ucdavis.edu>> wrote:
>>>
>>>
>>> On Sat, Nov 22, 2014 at 12:48 AM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote:
>>>
>>>> On Nov 21, 2014, at 3:35 PM, Daniel DeFreez <dcdefreez at ucdavis.edu <mailto:dcdefreez at ucdavis.edu>> wrote:
>>>>
>>>>> I believe with your patch, the node will get added, but the definition used will not have the body attached to it, so the analyzer will not process the body.
>>>>>
>>>>> Hmm, doesn't the analyzer itself use getBody() to access the body, thereby walking the list of redeclarations? It seems like it is still processing the body of the function, but maybe I don't know what to look for.
>>>>
>>>> This is a good point. We might not be gaining anything by replacing the decl with the one that has a body since getBody is guaranteed to search the redeclarations regardless.
>>>>
>>>> How about just removing both calls to isThisDeclarationADefinition() (from includeInGraph) and replacing the call to getBody with hasBody (to avoid the unnecessary AST de-serialization of the body)? That should work and would simplify the function greatly. What do you think?
>>>>
>>>> I think replacing getBody() with hasBody() is a good idea regardless of the approach taken to fix the missing edges. And avoiding node replacement would make it cleaner.
>>>>
>>>>
>>>> I am not sure why some of the checks in your first patch were necessary (like this one).
>>>> + // Skip definitions with previous declarations
>>>> + if (FD->getPreviousDecl())
>>>> + return false;
>>>> +
>>>>
>>>>
>>>> The reason I put that in was to avoid inserting redundant nodes. Just removing isThisDeclarationADefinition() yields:
>>>>
>>>
>>> Oh, I see! getOrInsertNode() would not insert an existing declaration, but it does not check for re-declarations.
>>>
>>> But would your approach work for this set?
>>> void a();
>>> void a() { }
>>> void b() { a(); } // Here, a call to "a()" might not be added since "a()" has a previous declaration.
>>>
>>> Alas, yes, you're right. I can't believe I didn't try that. Not going to work.
>>>
>>> Sounds like we would want to store canonical declarations, which brings us back to the suggestion of using "hasBody(Definition)" and only store the definitions that have bodies. Changing the signature of "includeInGraph" so that it mutates the Decl is fine; though, you might want to rename it as well.
>>>
>>>
>>> Yep. The problem isn't with includeInGraph, though. It's with hasBody(Definition). Since it takes a reference to a pointer-to-const, using it get the canonical declaration means the canonical declaration itself must be const. So pretty much all of the Decl* in CallGraph would have to get changed to const.
>>>
>>> I only know of two ways around it:
>>> 1) Change the FunctionDecl class
>>> 2) Walk redecls in some fashion similar to my second patch, which essentially just re-implemented hasBody without forcing the declaration to be const.
>>>
>>> Any other way?
>>
>>
>> Looks like we can use getCanonicalDecl() instead (in both FunctionDecl and ObjCMethodDecl case).
>>
>>
>> Ah! Excellent. How aptly named :)
>>
>
> :)
>
> I'll be on vacation next week.
>
> Seems like we have a solution here. I might be able to approve the patch, but won't be able to apply it. You should send the patch to cfe-dev and CC me.
>
> Thank you!
> Anna.
>
>> Many thanks.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141215/345b2280/attachment.html>
More information about the cfe-dev
mailing list