-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 16.10.2011 07:18, schrieb Lin Rongrong: > Results tried with "--oldralloc": > code0 data code1 code2 code3 code4 code5 code6 code7 code > 1C8D 1A90 4661 525B 47A7 50A5 55D0 4354 5625 1BB0 // ar168g sip > 0.55.006 sdcc 3.0.1 > 1BFC 1A90 476C 5042 489D 5213 5612 452D 57DC 1B7E // ar168g sip > 0.55.008 sdcc 3.0.6 #6969 > 1BB4 1A90 45EE 4ECA 4630 51D8 52A4 4A17 5310 1B65 // ar168g sip > 0.55.009 sdcc 3.0.6 #6969 --max-allocs-per-node 10000 > 1C4A 1A90 465E 5299 473A 51FB 560E 4378 5691 1BDD // ar168g sip > 0.55.010 sdcc 3.0.6 #6969 --oldralloc > > The annoying thing is, "--oldralloc" generated some wrong code which broken > the tcp implementation. I noticed this a month ago, now it still here. I do > not know how long we will maintain "--oldralloc" option, shoule debug it or > not?
Well, the bug could be in some part other than the register allocator, typically code generation. That means it could occour for some other code even with the new allcoator. A bug report with a minimal code example to reproduce the bug would thus be useful. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6auScACgkQbtUV+xsoLpry1ACeKKAc7R1bJqra4zsZkon65ihj Qr0AoJjzvnpRfVWz419SyTk+hW8o4LW5 =y+bR -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
