Processing behavior of .gnu.sgstubs in linker script
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNU Arm Embedded Toolchain |
New
|
Undecided
|
Unassigned | ||
Bug Description
When we use the arm-none-eabi tool chain to develop Cortex-M33, we encountered the following questions, please help us to answer them.
1. Since b.w has a limited jump range, is there a range for NSC to jump to Secure code? Their jump range is plus or minus 16MB, right?
2. When using the NSC function, the linker will generate a special .gnu.sgstubs Output Section. But we found through experiments that the section size calculated by recording the VMA at the beginning and end of the Output Section is different from the Seciton Size calculated outside the Output Section using the SIZEOF function built in the linker script! Why does this happen? Are there any side effects of using SIZEOF to calculate?
Thank you for your kind reply and help.
The version of the toolchain we use is "arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]".
The version of the server is "3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux".
| description: | updated |
| information type: | Public → Public Security |
| information type: | Public Security → Private Security |
| information type: | Private Security → Public |
| description: | updated |
