From: SourceForge.net <no...@so...> - 2006-10-05 22:09:53
|
Bugs item #1571773, was opened at 2006-10-06 00:09 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=1571773&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: linker Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Pisa (ppisa) Assigned to: Nobody/Anonymous (nobody) Summary: Aslink absolute code sections shift if packflag (-Y) is not Initial Comment: Aslink absolute code sections shift if packflag (-Y) is not set. Aslink linker behaves incorrectly for MCS51 target when more .REL files with absolute CODE sections are linked if SDCC --no-pack-iram option is set => the aslink -Y option is omitted. The attached example contains two assembly files with absolute sections and "build.sh" command. The output hexadecimal file .OUT or .IHX shows the problem by shifting of absolute section of the second .REL file from 0x0010 to 0x0013 which is incorrect. Affected SDCC version. SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Sep 8 2006) (UNIX) The whole affected project sources could be found in uLan project CVS repository at SF page. http://sourceforge.net/projects/ulan Thanks for your care in advance Pavel Pisa ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-10-06 05:40:35
|
Bugs item #1571773, was opened at 2006-10-06 00:09 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&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: linker Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Pisa (ppisa) Assigned to: Nobody/Anonymous (nobody) Summary: Aslink absolute code sections shift if packflag (-Y) is not Initial Comment: Aslink absolute code sections shift if packflag (-Y) is not set. Aslink linker behaves incorrectly for MCS51 target when more .REL files with absolute CODE sections are linked if SDCC --no-pack-iram option is set => the aslink -Y option is omitted. The attached example contains two assembly files with absolute sections and "build.sh" command. The output hexadecimal file .OUT or .IHX shows the problem by shifting of absolute section of the second .REL file from 0x0010 to 0x0013 which is incorrect. Affected SDCC version. SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Sep 8 2006) (UNIX) The whole affected project sources could be found in uLan project CVS repository at SF page. http://sourceforge.net/projects/ulan Thanks for your care in advance Pavel Pisa ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2006-10-06 07:40 Message: Logged In: YES user_id=888171 This is probably true, but why not just use the default? It is my intention to remove --no-pack-iram in the future instead of fixing it and keep two versions around. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&group_id=599 |
From: SourceForge.net <no...@so...> - 2006-10-06 21:10:34
|
Bugs item #1571773, was opened at 2006-10-06 00:09 Message generated for change (Comment added) made by ppisa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&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: linker Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Pisa (ppisa) Assigned to: Nobody/Anonymous (nobody) Summary: Aslink absolute code sections shift if packflag (-Y) is not Initial Comment: Aslink absolute code sections shift if packflag (-Y) is not set. Aslink linker behaves incorrectly for MCS51 target when more .REL files with absolute CODE sections are linked if SDCC --no-pack-iram option is set => the aslink -Y option is omitted. The attached example contains two assembly files with absolute sections and "build.sh" command. The output hexadecimal file .OUT or .IHX shows the problem by shifting of absolute section of the second .REL file from 0x0010 to 0x0013 which is incorrect. Affected SDCC version. SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Sep 8 2006) (UNIX) The whole affected project sources could be found in uLan project CVS repository at SF page. http://sourceforge.net/projects/ulan Thanks for your care in advance Pavel Pisa ---------------------------------------------------------------------- >Comment By: Pavel Pisa (ppisa) Date: 2006-10-06 23:10 Message: Logged In: YES user_id=523128 Thanks for reply. We have been forced to use --no-pack-iram for older SDCC/aslink versions because internal memory has not preserved required space for bit flags and probably even for some other problems with absolute sections in older SDCC versions. I am leaving for week now but Petr Smolik will check if build without --no-pack-iram result in correct memory layout for new SDCC versions. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-10-06 07:40 Message: Logged In: YES user_id=888171 This is probably true, but why not just use the default? It is my intention to remove --no-pack-iram in the future instead of fixing it and keep two versions around. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&group_id=599 |
From: SourceForge.net <no...@so...> - 2010-09-27 16:38:57
|
Bugs item #1571773, was opened at 2006-10-06 00:09 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&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: linker >Group: known bugs >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Pavel Pisa (ppisa) >Assigned to: Maarten Brock (maartenbrock) Summary: Aslink absolute code sections shift if packflag (-Y) is not Initial Comment: Aslink absolute code sections shift if packflag (-Y) is not set. Aslink linker behaves incorrectly for MCS51 target when more .REL files with absolute CODE sections are linked if SDCC --no-pack-iram option is set => the aslink -Y option is omitted. The attached example contains two assembly files with absolute sections and "build.sh" command. The output hexadecimal file .OUT or .IHX shows the problem by shifting of absolute section of the second .REL file from 0x0010 to 0x0013 which is incorrect. Affected SDCC version. SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Sep 8 2006) (UNIX) The whole affected project sources could be found in uLan project CVS repository at SF page. http://sourceforge.net/projects/ulan Thanks for your care in advance Pavel Pisa ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2010-09-27 18:38 Message: --no-pack-iram is deprecated in SDCC 2.9.7 #5996. ---------------------------------------------------------------------- Comment By: Pavel Pisa (ppisa) Date: 2006-10-06 23:10 Message: Logged In: YES user_id=523128 Thanks for reply. We have been forced to use --no-pack-iram for older SDCC/aslink versions because internal memory has not preserved required space for bit flags and probably even for some other problems with absolute sections in older SDCC versions. I am leaving for week now but Petr Smolik will check if build without --no-pack-iram result in correct memory layout for new SDCC versions. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-10-06 07:40 Message: Logged In: YES user_id=888171 This is probably true, but why not just use the default? It is my intention to remove --no-pack-iram in the future instead of fixing it and keep two versions around. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1571773&group_id=599 |