This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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: Gprof output in 2.21.1 different than in 2.21.53

From: Nick Clifton <nickc at redhat dot com>
To: Tamer <nuclearpsyche at gmail dot com>
Cc: binutils at sourceware dot org
Date: Tue, 25 Oct 2011 10:57:48 +0100
Subject: Re: Gprof output in 2.21.1 different than in 2.21.53
References: <E1452D45-A2F5-4F22-8712-3EBAB5AADCFD@gmail.com> <20111009033738.GD25970@bubble.grove.modra.org> <F5A43E1C-357B-4DB6-ABD0-110AAA28881D@gmail.com>

Hi Tamer,

Is there a place where those changes in gprof's output are documented?

Yes - gprof/bsd_callg_bl.m and gprof/gprof.texi.

I would like to know if I have to rewrite my parser

I think that you are going to have to rewrite/extend your parser.

What seems to have changes is the<cycle> tags.

Are you *sure* that the version of gprof that you are using is the only thing that has changed ?

The kind of output that you are describing can be generated by the 2.21.1 version of gprof. I suspect that what has actually changed is the compiler that you are using and that you are now seeing the results of function inlining that was not happening before.

Cheers
  Nick

References:
- Re: Gprof output in 2.21.1 different than in 2.21.53
  - From: Alan Modra
- Re: Gprof output in 2.21.1 different than in 2.21.53
  - From: Tamer

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