[gnu.g++] profiling in G++

gessel@cs.swarthmore.edu (Dan Gessel) (04/28/89)

Does anyone out there know if and when a version of g++ will come out
that supports profiling?

Dan

-- 
CS Net: gessel@cs.swarthmore.edu         
UUCP: {bpa,cbmvax,liberty}!swatsun!gessel

goss@ese.essex.ac.uk (Sanjiv Gossain) (05/11/89)

I recently remember seeing a posting asking whether
g++ would support profiling in the near future,
but I don't remember seeing a reply. Does anyone
know the answer?


Sanjiv Gossain
ESE Dept.
University Of Essex
Colchester CO4 3SQ 
UK

goss%ese.essex.ac.uk@nsfnet-relay.ac.uk

tiemann@YAHI.STANFORD.EDU (Michael Tiemann) (05/11/89)

The answer is that I don't have time to work on it.  Someone must
write a gcrt0.c which performs appropriate startup code.

A C++-style alternative is to write a profiling object which does the
right things, and whos constructor starts the right routines.  By
linking such an object in with the code, it C++ global constructor
will be called, starting the profiling monitor, and all should be
peachy keen.  The destructor should write out the data it collected
during the run, and put it in a file, e.g., gmon.out.  This would make
a nice addition to libg++.

Michael

becher@armada.UUCP (Jonathan D. Becher) (06/06/89)

Okay, so I've been successfully using G++ as my C++ compiler of 
choice for about a year.  I've had a couple of problems - but very 
few of them weren't fixed in the next release or I couldn't figure 
out my own workaround.  Now, my code is fairly robust, I'm trying 
to speed it up, so I go to turn on profiling.  Surprise!  "Profiling 
not yet supported in GNU C++".

So, the question of the hour is:  When will profiling be supported?
Michael?  Anyone else?  I suppose I could break out the documentation
on monitor and write my own - but maybe somebody has already done
the work for me.

Jon Becher
argosy!becher@decwrl.dec.com

"A man can never be too lazy or too