sorry that should have been 'prof' or 'gprof'.
> If you know the C code is the bottleneck then use prof or
> grof with the generated object.
>
> Though, more generally this does bring up the topic pre/post
> compilation hooks...
>
> ________________________________
> Glen Coakley, Sr. Software Engineer
> MQSoftware Inc., (763) 543-4845
> "Tinkero ergo sum." -- Chuck Murcko
>
>
> > -----Original Message-----
> > From: Inline Reader [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 17, 2001 1:18 PM
> > To: [EMAIL PROTECTED]
> > Subject: profiling inlined C
> >
> >
> >
> > I don't know about everyone else, but I'm turning into a
> speed freak.
> >
> > Sombody tell me pretty please how I can profile my inlined C
> > code, since it
> > is (horrors!) still most of the bottleneck to my entire
> > program (though
> > 1/25th of the bottleneck it used to be, hee hee).
> >
> > I really like Niel's way of debugging Perl and C
> > concurrently. Now after
> > stepping through the entire thing it would be nice to have
> > the corresponding
> > combined profile tool...
> >
> > Anyone up to the challenge?
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
>
