Quoting "Dmitry K." <[EMAIL PROTECTED]>:
Hi Paulo, hi all.
Hi, Dmitry
Very good work!
Thanks :)
Possible, you are work with 4.2.2 ? And is it possible to apply yours 'avrtest' to avr-gcc 4.1.2 version?
It should apply to any avr-gcc version (and even other compilers, for that matter)...
I have try quickly, results are strange: unexpected abort in both small programs (avr-gcc 4.1.2, -Os, -mmcu=atmega128). Below are both programs with compiler listing.
Thanks for reporting this. Using your simple test case I was able to find out the (brown paper) bug :P
Attached is a new version with the correction, that runs your test case just fine.
For extra debug information, you can uncomment the line (in "log_dump_line()"):
//printf("%s\n", log_data[cur_log_pos]);
I'm starting to build a simple debug log, that can be used to track
down why a test case ABORTED, by showing the last N instructions
executed with the values moved from where to where.
The output is still very raw, but I intend to improve it at least by using symbolic constants (Rn, SREG, etc.).
Enjoy, -- Paulo Marques ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
avrtest.tar.gz
Description: GNU Zip compressed data
_______________________________________________ AVR-GCC-list mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
