Re: FPS

[Mihai Bazon <mishoo infoiasi ro>]

I know man, just kidding :)  But even with those two extra parameters, I
had no enough patience to keep my hand on enter, so when gdb counted about
120000 calls I stopped.  And may I add that normally the compiler should
have been optimizing that code, such as the parameters were passed in
registers (of course, I didn't check...)

But, if you want to count # of stack frames, why not use a static counter
and get it's value from core using gdb?  It wouldn't slow down very much..

These being said, I think the discussion can stop here.. :)  However it's
no help for the man that asked "how many FPS..."

On Wed, 13 Jun 2001 16:29:09 +0300
Bohdan Vlasyuk <bohdan kivc vstu vinnica ua> wrote:

> On Wed, Jun 13, 2001 at 04:21:44PM +0300, Mihai Bazon wrote:
>
> > Hmm..  May I add some little optimization?
> >
> >   int main(int argc, char **argv) {
> >       return main(argc, argv);
> >   }
> that's actually bad optimization -- instead of just calling (void)
> function, you put that int and **char into stack, thus wasting time.
> Remember -- we aim best FPS, not smallest size.
>
> BTW -- there's one flaw in this solution -- backtracing in gdb is
> somewhat bad -- thus it taked much time to bt your core, even if
> started with -q --bath and `r;bt' are in .gdbinit


-- 
/*   -*- Mishoo -*-         In the beginning there was nothing,
 *  mishoo websci ro      which exploded.   (The Big Bang Theory)  */