Article View: gnu.gcc.help
Article #50333Re: Static analysis of g++ call flow
From: Richard Stallman
Date: Fri, 08 Oct 1993 15:39
Date: Fri, 08 Oct 1993 15:39
20 lines
1294 bytes
1294 bytes
A source-scanning cross-referencer can handle ordinary use of macros
well. It can find calls made via macros by scanning the macro bodies.
It would record them as calls "from the macros".
Thus, if you have this code:
#define foo bar (x)
mumble ()
{
foo
}
the output will say that mumble uses foo, and foo uses bar.
A source-scanning cross-referencer can be fooled by token-pasting or
by other strange usage in macros. The best solution is to minimize
such usage, and design it carefully so that you will get reasonable
results from cross-reference. That is, at least, practical--avoiding
conditionals is not practical.
Technical Details
Message-ID:
<9310081534.AA25152@mole.gnu.ai.mit.edu>Path:
arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!rmsReferences:
<9310081453.AA03989@quaestor>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,b96c32e932f5d2d3 X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1993-10-08 08:52:08 PST Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!rms From: rms@gnu.ai.mit.edu (Richard Stallman) Newsgroups: gnu.gcc.help Subject: Re: Static analysis of g++ call flow Date: 8 Oct 1993 11:39:06 -0400 Organization: GNUs Not Usenet Lines: 21 Sender: daemon@cis.ohio-state.edu Distribution: gnu Message-ID: <9310081534.AA25152@mole.gnu.ai.mit.edu> References: <9310081453.AA03989@quaestor>