From: SourceForge.net <no...@so...> - 2007-11-13 14:45:46
|
Support Requests item #1831117, was opened at 2007-11-13 17:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-14 08:15:34
|
Support Requests item #1831117, was opened at 2007-11-13 15:45 Message generated for change (Comment added) made by patryks You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 09:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-14 19:03:46
|
Support Requests item #1831117, was opened at 2007-11-13 17:45 Message generated for change (Comment added) made by stsp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Stas Sergeev (stsp) Date: 2007-11-14 22:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 11:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-14 20:34:33
|
Support Requests item #1831117, was opened at 2007-11-13 15:45 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 21:34 Message: Logged In: YES user_id=888171 Originator: NO Stas, Unless I fully misunderstand your request, the symbols in the RFE Patryk pointed to you are exactly what you're looking for. The map file already has the symbols representing the start and length of the various segments. Unfortunately these can currently only be accessed from assembly and not from C. That's why Patryk asked them to be renamed in the RFE. I'm sure he would also like them in a header file, but that's an extra. Maarten ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 20:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 09:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-14 21:20:08
|
Support Requests item #1831117, was opened at 2007-11-13 17:45 Message generated for change (Comment added) made by stsp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Stas Sergeev (stsp) Date: 2007-11-15 00:20 Message: Logged In: YES user_id=501371 Originator: YES There are symbols that are accessable from C - those that Patryk listed in *this* report, are. So I was looking among those. Now I see the rest, thanks! But I think a few symbols are still missing. For example, what would be a reliable way of calculating the firmware size? Looks like I need to summ quite a few l_XXX values to get that done. Wouldn't it be better to have something like __code_end, __data_end, __firmware_end etc? With gcc I don't need to calculate anything. Taking an address of an appropriate symbol does the trick. So that's why I haven't payed any attention to these constants that the aslink (or whoever) defines. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 23:34 Message: Logged In: YES user_id=888171 Originator: NO Stas, Unless I fully misunderstand your request, the symbols in the RFE Patryk pointed to you are exactly what you're looking for. The map file already has the symbols representing the start and length of the various segments. Unfortunately these can currently only be accessed from assembly and not from C. That's why Patryk asked them to be renamed in the RFE. I'm sure he would also like them in a header file, but that's an extra. Maarten ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 22:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 11:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-14 21:48:05
|
Support Requests item #1831117, was opened at 2007-11-13 15:45 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 22:48 Message: Logged In: YES user_id=888171 Originator: NO You guessed right about aslink creating the symbols :-) And adding lengths does not necessarily give the correct result because the segments can be non-adjacent. I guess you're looking for something like a high-water-mark? Btw. What is the difference between __code_end and __firmware_end? Could you also give an example of what you would like to use them for? ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 22:20 Message: Logged In: YES user_id=501371 Originator: YES There are symbols that are accessable from C - those that Patryk listed in *this* report, are. So I was looking among those. Now I see the rest, thanks! But I think a few symbols are still missing. For example, what would be a reliable way of calculating the firmware size? Looks like I need to summ quite a few l_XXX values to get that done. Wouldn't it be better to have something like __code_end, __data_end, __firmware_end etc? With gcc I don't need to calculate anything. Taking an address of an appropriate symbol does the trick. So that's why I haven't payed any attention to these constants that the aslink (or whoever) defines. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 21:34 Message: Logged In: YES user_id=888171 Originator: NO Stas, Unless I fully misunderstand your request, the symbols in the RFE Patryk pointed to you are exactly what you're looking for. The map file already has the symbols representing the start and length of the various segments. Unfortunately these can currently only be accessed from assembly and not from C. That's why Patryk asked them to be renamed in the RFE. I'm sure he would also like them in a header file, but that's an extra. Maarten ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 20:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 09:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2007-11-15 10:57:54
|
Support Requests item #1831117, was opened at 2007-11-13 17:45 Message generated for change (Comment added) made by stsp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Stas Sergeev (stsp) Date: 2007-11-15 13:57 Message: Logged In: YES user_id=501371 Originator: YES > And adding lengths does not necessarily give the correct result because > the segments can be non-adjacent. Yep, that was adding to my reservations about the aforementioned consts too. > Btw. What is the difference between __code_end and __firmware_end? __code_end may mark the end of the code, but the constant data can be put after the code for instance, and then __code_end != firmware_end. > Could you also give an example of what you would like to use them for? The use is pretty much straight-forward: I have atmega128 connected to at8252 via SPI. atmega128 can therefore read and write the firmware. They also communicate a lot. Instead of reading the entire flash, it might be a good idea for atmega128 to first ask at8252 about its firmware size, and read only that. And if it doesn't properly respond - no problems, then we don't even need to read that firmware, as it is broken. So adding just __firmware_end may be enough for my current needs, but it might be better to add some more delimiters, the way gcc (or is it ld?) does. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-15 00:48 Message: Logged In: YES user_id=888171 Originator: NO You guessed right about aslink creating the symbols :-) And adding lengths does not necessarily give the correct result because the segments can be non-adjacent. I guess you're looking for something like a high-water-mark? Btw. What is the difference between __code_end and __firmware_end? Could you also give an example of what you would like to use them for? ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-15 00:20 Message: Logged In: YES user_id=501371 Originator: YES There are symbols that are accessable from C - those that Patryk listed in *this* report, are. So I was looking among those. Now I see the rest, thanks! But I think a few symbols are still missing. For example, what would be a reliable way of calculating the firmware size? Looks like I need to summ quite a few l_XXX values to get that done. Wouldn't it be better to have something like __code_end, __data_end, __firmware_end etc? With gcc I don't need to calculate anything. Taking an address of an appropriate symbol does the trick. So that's why I haven't payed any attention to these constants that the aslink (or whoever) defines. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 23:34 Message: Logged In: YES user_id=888171 Originator: NO Stas, Unless I fully misunderstand your request, the symbols in the RFE Patryk pointed to you are exactly what you're looking for. The map file already has the symbols representing the start and length of the various segments. Unfortunately these can currently only be accessed from assembly and not from C. That's why Patryk asked them to be renamed in the RFE. I'm sure he would also like them in a header file, but that's an extra. Maarten ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 22:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 11:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200599&aid=1831117&group_id=599 |
From: SourceForge.net <no...@so...> - 2011-11-05 09:35:04
|
Feature Requests item #1831117, was opened at 2007-11-13 06:45 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350599&aid=1831117&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stas Sergeev (stsp) Assigned to: Nobody/Anonymous (nobody) Summary: section delimiters Initial Comment: Hi. gcc defines symbols like __data_load_start, __etext etc, so that the program can find out the addresses and the sizes of its sections. Does sdcc have something similar? And if not - this should be a Feature Request. At least I wan't able to find the like symbols in the map file. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2011-11-05 02:35 Message: I moved this to feature requests. ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-15 02:57 Message: Logged In: YES user_id=501371 Originator: YES > And adding lengths does not necessarily give the correct result because > the segments can be non-adjacent. Yep, that was adding to my reservations about the aforementioned consts too. > Btw. What is the difference between __code_end and __firmware_end? __code_end may mark the end of the code, but the constant data can be put after the code for instance, and then __code_end != firmware_end. > Could you also give an example of what you would like to use them for? The use is pretty much straight-forward: I have atmega128 connected to at8252 via SPI. atmega128 can therefore read and write the firmware. They also communicate a lot. Instead of reading the entire flash, it might be a good idea for atmega128 to first ask at8252 about its firmware size, and read only that. And if it doesn't properly respond - no problems, then we don't even need to read that firmware, as it is broken. So adding just __firmware_end may be enough for my current needs, but it might be better to add some more delimiters, the way gcc (or is it ld?) does. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 13:48 Message: Logged In: YES user_id=888171 Originator: NO You guessed right about aslink creating the symbols :-) And adding lengths does not necessarily give the correct result because the segments can be non-adjacent. I guess you're looking for something like a high-water-mark? Btw. What is the difference between __code_end and __firmware_end? Could you also give an example of what you would like to use them for? ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 13:20 Message: Logged In: YES user_id=501371 Originator: YES There are symbols that are accessable from C - those that Patryk listed in *this* report, are. So I was looking among those. Now I see the rest, thanks! But I think a few symbols are still missing. For example, what would be a reliable way of calculating the firmware size? Looks like I need to summ quite a few l_XXX values to get that done. Wouldn't it be better to have something like __code_end, __data_end, __firmware_end etc? With gcc I don't need to calculate anything. Taking an address of an appropriate symbol does the trick. So that's why I haven't payed any attention to these constants that the aslink (or whoever) defines. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2007-11-14 12:34 Message: Logged In: YES user_id=888171 Originator: NO Stas, Unless I fully misunderstand your request, the symbols in the RFE Patryk pointed to you are exactly what you're looking for. The map file already has the symbols representing the start and length of the various segments. Unfortunately these can currently only be accessed from assembly and not from C. That's why Patryk asked them to be renamed in the RFE. I'm sure he would also like them in a header file, but that's an extra. Maarten ---------------------------------------------------------------------- Comment By: Stas Sergeev (stsp) Date: 2007-11-14 11:03 Message: Logged In: YES user_id=501371 Originator: YES Thanks for the pointer. As far as I understand, you only want the declarations in the header files for the symbols already present. What I want is a new symbols. I need the symbols in the beginning and the end of the code and data sections. The internal symbols you pointed, are unfortunately of no use for me. ---------------------------------------------------------------------- Comment By: Patryk (patryks) Date: 2007-11-14 00:15 Message: Logged In: YES user_id=1788180 Originator: NO See my request: http://sourceforge.net/tracker/?func=detail&atid=350599&aid=1716427&group_id=599 Put a comment there and maybe it will brought more attention to some developer. Other symbols found in main.asm: __sdcc_external_startup __interrupt_vect __sdcc_gsinit_startup __sdcc_program_startup __start__stack __mcs51_genXINIT __mcs51_genXRAMCLEAR __mcs51_genRAMCLEAR __sdcc_program_startup ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350599&aid=1831117&group_id=599 |