Re: any performance profiling tools ??

dccoote@werple.mira.net.au (David Coote)
28 Sep 1997 23:16:02 -0400

          From comp.compilers
Related articles
any performance profiling tools ?? chunghsu@george.rutgers.edu (1997-09-23)
Re: any performance profiling tools ?? dccoote@werple.mira.net.au (1997-09-28)
Re: any performance profiling tools ?? everhart@gce.com (Glenn Everhart) (1997-09-30)
Re: any performance profiling tools ?? cfc@world.std.com (1997-10-01)
Re: any performance profiling tools ?? steve@blighty.com (1997-10-01)
Re: any performance profiling tools ?? ok@cs.rmit.edu.au (1997-10-02)
(fwd) Re: any performance profiling tools ?? koopman@cmu.edu (Philip Koopman) (1997-10-02)
Re: any performance profiling tools ?? sanjay@src.dec.com (1997-10-02)
[1 later articles]
| List of all articles for this month |
From: dccoote@werple.mira.net.au (David Coote)
Newsgroups: comp.compilers,comp.arch,comp.benchmarks
Date: 28 Sep 1997 23:16:02 -0400
Organization: werple public-access Internet
References: 97-09-084
Keywords: performance, architecture

Two tools exist on the DEC Alpha under DEC UNIX to do this sort of
stuff. The uprofile tool and the Digital Continuous Profiling
Infrastructure (DCPI).


On a slightly different note, DEC also has ATOM, a very nice profiling
tool-suite. This has some supported tools, some unsupported tools that
give some guidance on how to "roll-your-own" tools, and a tool
building kit. As a completely unsolicited testimonial, at first glance
under DEC UNIX 4.0b the ATOM tool suite seems to work with GNAT Ada
3.10/3.11. Anyone who has tried to get third-party
profiling/performance analysis tools working with Ada development
environments will appreciate that.


In article 97-09-084, chunghsu@george.rutgers.edu says...
>... I am wondering if there is any tool which can profile
>performance information such as the number of cache misses by
>really executing the code on a particular machine (say SUN sparc-10
>with superSPARC-II cpu's).
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.