This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: basic-block profiling

From: Saisanthosh Balakrishnan <sai at cs dot wisc dot edu>
To: Daniel Jacobowitz <drow at mvista dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 28 Oct 2002 12:58:03 -0600
Subject: Re: basic-block profiling
References: <20021028122942.B16605@solinus.cs.wisc.edu> <20021028123638.C16605@solinus.cs.wisc.edu> <20021028184359.GA12380@nevyn.them.org>

> You're looking for -fprofile-arcs and -ftest-coverage in GCC 3.2; those
> are the new block (edge, really) profiler.

I'm aware of those two flags. But, is gcov capable of producing output
similar to bb.out (i.e. not produce simple.c.gcov, but give per bb
info) ?  From my understanding, it cannot. So, I'd have to use the
.bb, .bbg and .da files to get such info.

This leads me to an other question, can gcov produce annotated .s
file (simple.s.gcov) instead of simple.c.gcov?

IMHO, if -a, and -ax were removed, the documentation should have been
updated.

-Sai

Follow-Ups:
- Re: basic-block profiling
  - From: Janis Johnson

References:
- basic-block profiling
  - From: Saisanthosh Balakrishnan
- Re: basic-block profiling
  - From: Saisanthosh Balakrishnan
- Re: basic-block profiling
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]