Re: [avr-gcc-list] binutils/.../testsuite/avr

[E. Weddington]

Klaus Rudolph wrote:

> Hi all,
>
> > On the other hand, binutils and gcc just spit out a file. As such, there
> > should be no need for a simulator for the most part. It's just a matter
> > of compiling or assembling a chunk of code and then comparing the output
> > to some expected result. The output used for the compare could either be
> > the raw intermediate asm file for a C code fragment or possibly a
> > disassemle of the object file.
> >  
> I think that is ok for assembler but never for C/C++. If you change 
> something in gcc maybe a better optimizer
> the code is valid but the comparisson against a older file is not ok. 
> So a simulation is needed
> to check that the code *do* the same and not *look* the same. :-)

I'm sure it would be educational to take a look and see how other ports 
do it, such as arm, since it is a very mature port and there are a lot 
of developers working on it.