From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,32397e53f83af42a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-27 15:01:39 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!nnxp1.twtelecom.net!216.170.153.135.MISMATCH!tdsnet-transit!newspeer.tds.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: profiler Date: 27 Oct 2003 17:01:36 -0600 Organization: LJK Software Message-ID: References: <8ylmb.9212$mZ5.51086@attbi_s54> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1067295672 19471 192.135.80.34 (27 Oct 2003 23:01:12 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Mon, 27 Oct 2003 23:01:12 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:1751 Date: 2003-10-27T17:01:36-06:00 List-Id: In article , Stephen Leake writes: > But why are you profiling a non-specific compiler? Profiling is only > necessary when you have a performance problem; Profiling to let you know how much time is spent in various routines and shareable images can be used to characterize a workload, when one does not have better tools.