gtags-cscope/global finds incorrect callers

rail shafigulin <[email protected]>
Newsgroups gmane.comp.gnu.global.bugs
Message-ID <CAFAaeRVL6pAaNWfBh0dZpKWu_xYHiYHz++97C72nj9Mx6paj7Q@mail.gmail.com>
I'm navigating through https://github.com/openrisc/llvm-or1k

I've connected the GTAGS database to my Vim using
:cs add GTAGS
and set my cscope program to gtags-cscope using
:set cscopeprg=gtags-cscope
just like it is stated in the manual.

I've tried to do a caller search for releaseSucc using the following command
:cs f c releaseSucc

The output looked like the following:

llvm-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
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-global
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.