RE: [avr-gcc-list] testsuite saga continues

[Wouter van Gulik]

> The logging version will always be slower. This is not just a matter of
> "outputting" the log, it is also a matter of "building" the log.
> 
> We can avoid the "output" cost by only printing the last N lines, but we
> can not avoid the build cost. The code to do this was there at some
> point, but I decided to remove it, because under Linux you probably can
> do the same by running "avrtest_log test_program | tail -n N" and it
> should run almost as fast as a native solution.
> 

The only information you print is register info right? Since the parsing is
so heavy does it make sense to save the complete register file (up to SPH).
And then parse afterwards? It is "just" 96 bytes.
The only info missing would be addresses to/from memory, but that could be
ignored, since it's only load/store. When the address is absolutely
relevant, just re-run using log.
Just thinking out loud, it is probably nasty to create and the gain is
almost nothing...

> So, I can add a "--tail" option to the log version, but the naked
> version will never be able to print any log at all, so that it runs as
> fast as possible.
> 
> Remember that the main purpose of avrtest is to run gcc's testsuite.
> While running the testsuite, having a log is useless, but speed is
> important.
> 

Yes you are right, you can't have it all.

> BTW, I've done some more optimizations and the version I have now is
> almost twice as fast as the one on CVS, doing 30 P4 clocks per AVR
> clock, i.e., on my P4 3GHz I can simulate a 100MHz avr :)
> 
> 
> I don't have those numbers right now, but since there are tests that
> don't even fit in 128Kb of flash, there are probably some more that
> don't fit on 8Kb.
> 

Aha, well it is going to be hard to test the <8Kb then. Are these 128KB even
in an optimized? I can imagine not fitting when using -O0.

> >
> > Do you already have a format for doing this? XML based?
> 
> Nop. I haven't even started to think about the details.
> 
> I would give my full support to anyone trying to setup a benchmarking
> framework, though ;)
> 

Hmm, nope never done such a thing before. Let me first try to get gcc
compiling on my windows machine. It is a lot faster compared to my linux
machine (DualCore 2.1GHZ vs Duron 1.3 GHz)

Wouter