delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/02/23/11:58:38

Date: Tue, 23 Feb 1999 18:56:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Olivier Sohier <olivier DOT sohier AT sophia DOT europe DOT vlsi DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Profile info with GCC
In-Reply-To: <36D2BBE3.1952308B@sophia.europe.vlsi.com>
Message-ID: <Pine.SUN.3.91.990223185214.13729I-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com

On Tue, 23 Feb 1999, Olivier Sohier wrote:

> I am trying to get profile information with gcc.
> On SunOS, I'm using gcc version 2.7.2.1 with '-a' and '-g' options. The
> file 'bb.out' generated after execution contains the number of times
> each basic block is executed, and the C line number of the start of the
> basic block.

You are mixing two different things here.  If you need the run-time 
profile of a program, compile and link it with the -pg switch, run it, 
and then type "gprof program" to generate the profile.  The profile shows 
how much time, absolute and in percents, did every function take.  See 
chapter 13 of the DJGPP FAQ list for more details.

If you need a coverage info (i.e., how many times each block was 
executed), then currently you can't: `gcov', the GNU version of the 
coverage tool, is not ported to DJGPP.

> Why can't I get a 'bb.out' with gcc 2.6.3 ?

If I recall correctly, there was a bug in early versions of GCC ports to 
DJGPP which prevented bb.out from being created.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019