Richard Latter schrieb: > using PCW a friend has managed to produce a .hex file of 175 bytes as > opposed to the 820 generated by SDCC.
Comparing the size of Intel hex files is probably not what you want, because it only gives an estimate of the code size. *If* the extra '.' in line 93 is removed your code.c results in a hex file code.hex of 820 bytes. you can reduce this with > packihx code.hex >t.hex to 804 bytes. or with srec_cat (srecord.sf.net) > srec_cat code.hex -intel -o t.hex -intel to 712 bytes. or with extra options on the command line > srec_cat code.hex -intel -o t.hex -intel_hex_16 -Line_Length 127 to 648 bytes. and just for the record also increase with > srec_cat code.hex -intel -o t.hex -intel -Line_Length 20 to 1444 bytes. Compare the used addresses in the listing files of SDCC and PCW instead? 0x008e corresponds to 286 bytes = 2 bytes * (0x8e+1) A 175 bytes intel hex file generated by PCW would probably be equivalent to not more than about 80 bytes of code which would be an almost incredibly good result. (There are 42 assignments, 7 increments/decrements, an IRQ and 11 conditions in the c code and a pic opcode does not fit in a byte.) Eventually 175 byte should be compared to 286 byte? Greetings, Frieder Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
