> -----Original Message----- > From: > [email protected] > [mailto:simulavr-devel-bounces+eweddington=cso.atmel....@nongn > u.org] On Behalf Of Joerg Wunsch > Sent: Wednesday, March 11, 2009 7:53 AM > To: [email protected] > Subject: Re: [Simulavr-devel] avrtest and simulavr vs simulavrxx > > As Klaus Rudolph wrote: > > > >It's a fairly homegrown (of the old simulavr) text file. I'm > > >attaching one for reference. Also, it's always using a fixed name. > > > objdump will do the job as well. > > But again, since the simulator has the name "simulavr" (just as the > old one), any script using it might expect it behaving the same as the > older one used to. At the very least, that's what will cause the > smallest effort for anyone who's been using it inside scripts. > > For everything else, the first step has to be to detect which > simulator actually being faced with, and then act upon. objdump > itself is only part of the game, since its output would only generate > something that is similar to the older coredump format, but still > sufficiently different so you have to postprocess it anyway.
At this point, I think the only regular user of the old simulavr is the avr-libc regression tests. Since we control the scripts that run it, we can change it as necessary. I have not heard of the old simulavr being used widely in the field. I don't think we have to worry so much about backwards compatibility that it should hamper us from doing what's right. If simulavrxx is going to be developed to the point that it will subsume the old simulavr and avrtest, then I would like to change the name of it to just plain "simulavr" to avoid confusion. The "xx" part was just to show that it is developed in a C++ code base, but that doesn't matter to our end users. I would also like to see a release version of 1.0 *even if it's not perfect*. _______________________________________________ Simulavr-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/simulavr-devel
