From: SourceForge.net <no...@so...> - 2007-05-04 16:33:11
|
Bugs item #1712928, was opened at 2007-05-04 18:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: peephole optimizer Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Maarten Brock (maartenbrock) Assigned to: Nobody/Anonymous (nobody) Summary: Peephole rule 301 applied incorrectly Initial Comment: In the attached code the peephole rule 301 is applied where it should not be. I used the latest snapshot #4784 with the following options: SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c I consider this one a showstopper for release 2.7.0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-05-04 16:33:38
|
Bugs item #1712928, was opened at 2007-05-04 18:33 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: peephole optimizer Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Maarten Brock (maartenbrock) Assigned to: Nobody/Anonymous (nobody) Summary: Peephole rule 301 applied incorrectly Initial Comment: In the attached code the peephole rule 301 is applied where it should not be. I used the latest snapshot #4784 with the following options: SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c I consider this one a showstopper for release 2.7.0. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2007-05-04 18:33 Message: Logged In: YES user_id=888171 Originator: YES File Added: uip_arch_bad.asm ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 |
From: Borut R. <bor...@si...> - 2007-05-05 09:14:15
|
Maarten, is this a new bug, introduced after the sdcc 2.6.0 release? Will you handle it? For the sdcc 2.6.0 release you prepared the knownbugs.html document. Will you prepare it for 2.7.0 too? Do you have a special tool to generate it from the SF tracker? Borut SourceForge.net wrote: > Bugs item #1712928, was opened at 2007-05-04 18:33 > Message generated for change (Comment added) made by maartenbrock > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 > > Please note that this message will contain a full copy of the comment thread, > including the initial issue submission, for this request, > not just the latest update. > Category: peephole optimizer > Group: None > Status: Open > Resolution: None > Priority: 5 > Private: No > Submitted By: Maarten Brock (maartenbrock) > Assigned to: Nobody/Anonymous (nobody) > Summary: Peephole rule 301 applied incorrectly > > Initial Comment: > In the attached code the peephole rule 301 is applied where it should not be. > > I used the latest snapshot #4784 with the following options: > > SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c > > I consider this one a showstopper for release 2.7.0. > > ---------------------------------------------------------------------- > > >> Comment By: Maarten Brock (maartenbrock) >> > Date: 2007-05-04 18:33 > > Message: > Logged In: YES > user_id=888171 > Originator: YES > > File Added: uip_arch_bad.asm > > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > |
From: Borut R. <bor...@si...> - 2007-05-05 09:32:17
|
I found out that the rule 301 was added by Bernhard Held in sdcc revision #4540 on 30.12.2006, so it is probably a new bug. Can we just remove the rule from peeph.def? Borut Borut Razem wrote: > Maarten, > > is this a new bug, introduced after the sdcc 2.6.0 release? > Will you handle it? > > For the sdcc 2.6.0 release you prepared the knownbugs.html document. > Will you prepare it for 2.7.0 too? Do you have a special tool to > generate it from the SF tracker? > > Borut > > > SourceForge.net wrote: > >> Bugs item #1712928, was opened at 2007-05-04 18:33 >> Message generated for change (Comment added) made by maartenbrock >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 >> >> Please note that this message will contain a full copy of the comment thread, >> including the initial issue submission, for this request, >> not just the latest update. >> Category: peephole optimizer >> Group: None >> Status: Open >> Resolution: None >> Priority: 5 >> Private: No >> Submitted By: Maarten Brock (maartenbrock) >> Assigned to: Nobody/Anonymous (nobody) >> Summary: Peephole rule 301 applied incorrectly >> >> Initial Comment: >> In the attached code the peephole rule 301 is applied where it should not be. >> >> I used the latest snapshot #4784 with the following options: >> >> SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c >> >> I consider this one a showstopper for release 2.7.0. >> >> ---------------------------------------------------------------------- >> >> >> >>> Comment By: Maarten Brock (maartenbrock) >>> >>> >> Date: 2007-05-04 18:33 >> >> Message: >> Logged In: YES >> user_id=888171 >> Originator: YES >> >> File Added: uip_arch_bad.asm >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> sdcc-devel mailing list >> sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-devel >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > |
From: Maarten B. <sou...@ds...> - 2007-05-05 09:27:48
|
Borut, Yes this is a new bug. Rule 301 is one of the RemoveDeadMove optimizations introduced by Bernhard. I could look into it, but am still busy with the z80 peephole patches. I was hoping Berhard could have a look. If nothing else we can always disable the rule. I created the knownbugs.html by hand. I just saved the two pages, removed some stuff, merged them and replaced local links with external ones. I could do it again. Greetings, Maarten > Maarten, > > is this a new bug, introduced after the sdcc 2.6.0 release? > Will you handle it? > > For the sdcc 2.6.0 release you prepared the knownbugs.html document. > Will you prepare it for 2.7.0 too? Do you have a special tool to > generate it from the SF tracker? > > Borut > > > SourceForge.net wrote: > > Bugs item #1712928, was opened at 2007-05-04 18:33 > > Message generated for change (Comment added) made by maartenbrock > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 > > > > Please note that this message will contain a full copy of the comment thread, > > including the initial issue submission, for this request, > > not just the latest update. > > Category: peephole optimizer > > Group: None > > Status: Open > > Resolution: None > > Priority: 5 > > Private: No > > Submitted By: Maarten Brock (maartenbrock) > > Assigned to: Nobody/Anonymous (nobody) > > Summary: Peephole rule 301 applied incorrectly > > > > Initial Comment: > > In the attached code the peephole rule 301 is applied where it should not be. > > > > I used the latest snapshot #4784 with the following options: > > > > SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c > > > > I consider this one a showstopper for release 2.7.0. > > > > ---------------------------------------------------------------------- > > > > > >> Comment By: Maarten Brock (maartenbrock) > >> > > Date: 2007-05-04 18:33 > > > > Message: > > Logged In: YES > > user_id=888171 > > Originator: YES > > > > File Added: uip_arch_bad.asm > > > > ---------------------------------------------------------------------- > > > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > sdcc-devel mailing list > > sdc...@li... > > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: SourceForge.net <no...@so...> - 2007-05-05 16:48:07
|
Bugs item #1712928, was opened at 2007-05-04 18:33 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: peephole optimizer >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Maarten Brock (maartenbrock) >Assigned to: Maarten Brock (maartenbrock) Summary: Peephole rule 301 applied incorrectly Initial Comment: In the attached code the peephole rule 301 is applied where it should not be. I used the latest snapshot #4784 with the following options: SDCC -c --debug --model-large --std-sdcc99 --fverbose-asm uip\uip_arch_bad.c I consider this one a showstopper for release 2.7.0. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2007-05-05 18:48 Message: Logged In: YES user_id=888171 Originator: YES Fixed in SDCC 2.6.5 #4787. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-05-04 18:33 Message: Logged In: YES user_id=888171 Originator: YES File Added: uip_arch_bad.asm ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1712928&group_id=599 |