Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!YAHI.STANFORD.EDU!tiemann
From: tiemann@YAHI.STANFORD.EDU (Michael Tiemann)
Newsgroups: gnu.g++
Subject: Profiling in g++
Message-ID: <8905111601.AA01863@yahi.stanford.edu>
Date: 11 May 89 16:01:46 GMT
References: <918@servax0.ESSEX.AC.UK>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: tiemann@lurch.stanford.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 12

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