From: RONGRONG L. <wo...@pa...> - 2012-08-13 18:17:56
|
Great news. 3.2.0 release does not have the "AR168G keypad error" problem (with "--oldralloc" option). When I tried --nolospre option with 3.2.1 #8062, I got the old familiar error: C:\SDCC\BIN\sdcc menu.c -mz80 -c --std-c99 --oldralloc --nolospre --codeseg CODE4 menu.asm:3274: Error: <a> machine specific addressing or addressing mode error removing menu.rel ..\bin\make: *** [menu.rel] Error 1 where line 3274 in menu.asm is "jr 00107$" I do not have the hardware of the other 2 bugs in hand, will try 3.2.0 release on those tomorrow. Woody http://palmmicro.com/woody/ On 8/14/2012 1:07 AM, Philipp Klaus Krause wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 1) After the 3.2.0 release the smallopts and lospre branches have been > merged, which are naturally not tested as much as the older work in > trunk was at the time of the 3.2.0 release. Thus you might want to try > 3.2.0, too, when looking for the most bug-free version. > > 2) Can you track these bugs you discovered down to the point where you > can make bug reports at sourceforge for them? > > 3) You might want to try the --no-peep option to check if this is a > peephole issue, and the --nolospre option (in case it is a bug that > got introduced after the 3.2.0 release) to check if the bug is due to > the merge of the lospre branch. > > 4) I am happy to see that code size has gone down for you, even though > the difference is far less than what I see in my testcases. > > Philipp > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAlApNGsACgkQbtUV+xsoLpqhOwCdF9as0iyHVylvHpev4tvI75tk > bdkAnjTRCjr4kKbImggHAOk2/m9WB3Ol > =oHpN > -----END PGP SIGNATURE----- > |