|
From: | Shigio YAMAGUCHI |
Subject: | Re: gtags-cscope/global finds incorrect callers |
Date: | Fri, 25 Sep 2015 08:08:08 +0900 |
The output looked like the following::cs f c releaseSuccI've tried to do a caller search for releaseSucc using the following commandjust like it is stated in the manual.:set cscopeprg=gtags-cscopeand set my cscope program to gtags-cscope usingI've connected the GTAGS database to my Vim using:cs add GTAGSllvm-or1k/include/llvm/CodeGen/MachineScheduler.h|335| <<releaseSucc>> void releaseSucc(SUnit *SU, SDep *SuccEdge);
llvm-or1k/lib/CodeGen/MachineScheduler.cpp|539| <<releaseSucc>> releaseSucc(SU, &*I);
llvm-or1k/lib/CodeGen/SelectionDAG/ScheduleDAGVLIW.cpp|86| <<releaseSucc>> void releaseSucc(SUnit *SU, const SDep &D);
llvm-or1k/lib/CodeGen/SelectionDAG/ScheduleDAGVLIW.cpp|146| <<releaseSucc>> releaseSucc(SU, *I);Fist and third results are incorrect. They are declarations of these functions and not the callers.Output also doesn't seem to show what method calls a searched method. Note: <<releaseSucc>> releaseSucc(SU, *I); It would be nice to have something like <<ScheduleDAGVLIW::releaseSuccessors(SUnit *SU)>> releaseSucc(SU, *I)As an additional note:It would be nice to give the global tool awareness what function callers are being search for. The result above demonstrates that search found two methods named releaseSucc, one from ScheduleDAGMI class (2nd result) and one from ScheduleDAGVLIW class (4th result). If a user could pass information to the global tool stating that the user is looking for callers of ScheduleDAGVLIW::rereleaseSucc(...) instead of a caller of <any class>::releaseSucc(...), I believe this would be a very good improvement of the tool.
_______________________________________________
Bug-global mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-global
[Prev in Thread] | Current Thread | [Next in Thread] |