Article View: gnu.gcc.help
Article #50353Re: Static analysis of g++ call flow
From: Richard Stallman
Date: Mon, 11 Oct 1993 18:29
Date: Mon, 11 Oct 1993 18:29
16 lines
1457 bytes
1457 bytes
>If you rely on incomplete data for doing maintenance, bugs will
>result. When you change the way to call foo, you need to find *all*
>the calls, not just those that happen to be enabled on the target you
>are using today.
I belive the only downside of this is that you have to build
the call tree once for each target you are supporting. Its a
productivity hit but, in my mind this is a hit worth taking.
Consider a program like GCC that supports many dozens of targets.
This is not practical.
I can't tell you what program to write. (I almost said, "You can
write whatever you like," but that's not true any more--ask
lpf@uunet.uu.net about why it's not true.) All I can say is what sort
of cross-referencer I'd consider an enhancement to the GNU project.
Technical Details
Message-ID:
<9310111825.AA09747@mole.gnu.ai.mit.edu>Path:
arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!math.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!rmsReferences:
<9310111656.AA20698@TIS.COM>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-11 12:29:23 PST Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!math.ohio-state.edu!pacific.mps.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: 11 Oct 1993 14:29:53 -0400 Organization: GNUs Not Usenet Lines: 17 Sender: daemon@cis.ohio-state.edu Distribution: gnu Message-ID: <9310111825.AA09747@mole.gnu.ai.mit.edu> References: <9310111656.AA20698@TIS.COM>