linker-scripts

问题 I'm working on an Arm bare-metal application and I've marked some sections with NOLOAD . According to the explanation in Understanding linker script NOLOAD sections in embedded software , I expected the resulting ELF file to not have a loadable segment (program header) for these sections, but it does. Is this correct? Why are those sections marked as loadable in the ELF file? This is a part of my linker script: .bss (NOLOAD) : { . = ALIGN(4); __bss_start__ = .; *(.bss_begin .bss_begin.*) *(

问题 I'm working on an Arm bare-metal application and I've marked some sections with NOLOAD . According to the explanation in Understanding linker script NOLOAD sections in embedded software , I expected the resulting ELF file to not have a loadable segment (program header) for these sections, but it does. Is this correct? Why are those sections marked as loadable in the ELF file? This is a part of my linker script: .bss (NOLOAD) : { . = ALIGN(4); __bss_start__ = .; *(.bss_begin .bss_begin.*) *(

问题 Have a library os.lib which has many objects archived like kernel.o semaphor.o..etc need to place the specific section of object file in os.lib to a flash location using gcc linker script SECTIONS { .text : { os.lib:kernel.o(.text) } } But does not seem to work! ld throws error kernel.o not found. tried this and also archive:file mentioned in this does not work tool chain: arm-none-eabi-ld 来源： https://stackoverflow.com/questions/65092280/gcc-linking-specific-file-in-archive

来源： https://stackoverflow.com/questions/64078423/make-text-section-execute-only

来源： https://stackoverflow.com/questions/28688484/actual-default-linker-script-and-settings-gcc-uses

问题 I am getting a linking error: dangerous relocation: l32r: Literal placed after use: I am still trying to debug; however, I want to better understand this error. I understand what relocation is; however, I am not sure how it can be dangerous and was looking for some clarification. Also, a small code snippet that could generate this type of error would be helpful. In short, what is " a dangerous relocation "? 回答1: This is a two-part answer, as there are really two questions here, one general (

问题 What are general measures against the .text region not fitting into "iram1_0_seg" when linking for the ESP8266 using the xtensa GCC based toolchain? I guess that the ESP8266s RAM is not big enough to hold certain functions. However, what can I do to move as many functions into flash as possible? Here is an example of what the linker returns: /home/user/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/1.20.0-26-gb404fb9-2/bin/xtensa-lx106-elf-gcc -I/home/user/git/esp-open-sdk/sdk/include

问题 What is the usual suffix for a linker script so that VIM will use syntax-highlighting on it? 回答1: It seems to be .ld , only from what I see Vim doesn't come (at least mine doesn't, 7.3.) with the syntax files for it. Try the ones offered for download here. 来源： https://stackoverflow.com/questions/9612818/default-gnu-linker-script-name-so-vim-does-syntax-highlighting

问题 What is the usual suffix for a linker script so that VIM will use syntax-highlighting on it? 回答1: It seems to be .ld , only from what I see Vim doesn't come (at least mine doesn't, 7.3.) with the syntax files for it. Try the ones offered for download here. 来源： https://stackoverflow.com/questions/9612818/default-gnu-linker-script-name-so-vim-does-syntax-highlighting

问题 I viewed the source code of __libc_init_array from http://newlib.sourcearchive.com/documentation/1.18.0/init_8c-source.html . But I don't quite understand what this function does. I know that these symbols /* These magic symbols are provided by the linker. */ extern void (*__preinit_array_start []) (void) __attribute__((weak)); extern void (*__preinit_array_end []) (void) __attribute__((weak)); extern void (*__init_array_start []) (void) __attribute__((weak)); extern void (*__init_array_end [