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

[Paulo Marques]

Wouter van Gulik wrote:
> Paulo Marques schreef:
>
> > The program used more than 4k of stack? Yikes!
>
> Well I thinks it's the 64 bit stack bug... if anything goes wrong with 
> the stack you might end up having a huge stack. It's a bug in the program.

That makes sense.

> > > Can you make avrtest check on stack overflow?
> >
> > I can, specially if I start accepting command line arguments to define 
> > memory regions, so that I also know where the stack really ends.
> >
> > I'll post a new version as soon as I have this. In the meanwhile, you 
> > can work around that specific problem, by switching the addresses of 
> > the exit and the abort ports, so that the abort port is hit first ;)
>
> Yes I already thought about doing so.
>
> Could you then also print the real flash address of the exit just like 
> you do with the log.

The exit through the "exit port" already shows the address. Its only the 
exit through "rjmp +0" that doesn't. I'll change that to make it consistent.

> And the total number of cycles past.

The latest version in CVS already does that. Just use:

cvs -z3 -d:pserver:address@hidden:/cvsroot/winavr 
co -P avrtest

to check it out, and then a simple "cvs update" will be enough to always 
keep the latest version at hand.

BTW, Andrew sent me a test case he tried in both avrora and avrtest and 
the total cycle count matched almost exactly: 7934 cycles for avrora, 
7935 cycles for avrtest. I bet the one cycle difference is from the last 
OUT instruction, that avrora simply "breaks" before executing it, while 
avrtest actually "executes" it.

So, the cycle counts seem to be all correct now,

--
Paulo Marques
Software Development Department - Grupo PIE, S.A.
Phone: +351 252 290600, Fax: +351 252 290601
Web: www.grupopie.com

"Nostalgia isn't what it used to be."