michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/include/arch/arc/v2/linker.ld

268 lines
6.6 KiB
Text
Raw Normal View History

arc: add support for generic Add support for a "generic" ARC implementation. This is a misnomer since ARC platforms are synthesized by the SOC vendor and are specifc to a given vendors implementation/configuration. This platform support if for an SOC where we are allowed to let the code to support the SOC into the wild but not allowed to name it in public. This change allows to work on support for the SOC in the open and let the rest of the community see the evolution of of the platform. Change-Id: Idbb52fc80464ec04e91665871951f6ea79e5299d Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
2015-09-10 10:54:09 -07:00
/*
ARC: add linker script template for metware toolchain Add linker script template for MWDT toolchain (linker-mwdt.ld) Move linker.ld to linker-gnu.ld (without changes) The "linker.ld" is wraper now. Signed-off-by: Wayne Ren <wei.ren@synopsys.com>
2020-07-03 17:05:46 +08:00
* Copyright (c) 2020 Synopsys.
arc: add support for generic Add support for a "generic" ARC implementation. This is a misnomer since ARC platforms are synthesized by the SOC vendor and are specifc to a given vendors implementation/configuration. This platform support if for an SOC where we are allowed to let the code to support the SOC into the wild but not allowed to name it in public. This change allows to work on support for the SOC in the open and let the rest of the community see the evolution of of the platform. Change-Id: Idbb52fc80464ec04e91665871951f6ea79e5299d Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
2015-09-10 10:54:09 -07:00
*
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-18 17:01:01 -08:00
* SPDX-License-Identifier: Apache-2.0
arc: add support for generic Add support for a "generic" ARC implementation. This is a misnomer since ARC platforms are synthesized by the SOC vendor and are specifc to a given vendors implementation/configuration. This platform support if for an SOC where we are allowed to let the code to support the SOC into the wild but not allowed to name it in public. This change allows to work on support for the SOC in the open and let the rest of the community see the evolution of of the platform. Change-Id: Idbb52fc80464ec04e91665871951f6ea79e5299d Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
2015-09-10 10:54:09 -07:00
*/
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
/**
* @brief Common parts of the linker scripts for the ARCv2 targets for
* GNU and MWDT toolchains.
*/
#include <linker/sections.h>
#include <linker/linker-defs.h>
#include <linker/linker-tool.h>
/* physical address of RAM */
#ifdef CONFIG_HARVARD
#define ROMABLE_REGION ICCM
#define RAMABLE_REGION DCCM
#else
#if defined(CONFIG_XIP) && (FLASH_SIZE != 0)
#define ROMABLE_REGION FLASH
#define RAMABLE_REGION SRAM
#else
#define ROMABLE_REGION SRAM
#define RAMABLE_REGION SRAM
#endif
#endif
#ifdef CONFIG_ARC_MPU_ENABLE
#if CONFIG_ARC_MPU_VER == 2
#define MPU_MIN_SIZE 2048
arch: arc: add support of mpu v6 Add support of ARC mpu v6 * minimal region size down to 32 bytes * maximal region number up to 32 * not support uncacheable region and volatile uncached region * clean up mpu code for better readablity Signed-off-by: Yuguo Zou <yuguo.zou@synopsys.com>
2021-08-24 20:42:46 +08:00
#elif (CONFIG_ARC_MPU_VER == 3) || (CONFIG_ARC_MPU_VER == 4) || (CONFIG_ARC_MPU_VER == 6)
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
#define MPU_MIN_SIZE 32
#endif
#define MPU_MIN_SIZE_ALIGN . = ALIGN(MPU_MIN_SIZE);
#if defined(CONFIG_MPU_REQUIRES_POWER_OF_TWO_ALIGNMENT)
#define MPU_ALIGN(region_size) \
. = ALIGN(MPU_MIN_SIZE); \
. = ALIGN( 1 << LOG2CEIL(region_size))
#else
#define MPU_ALIGN(region_size) \
. = ALIGN(MPU_MIN_SIZE)
#endif
#else
#define MPU_MIN_SIZE_ALIGN
#define MPU_ALIGN(region_size) . = ALIGN(4)
#endif
arch: arc: add user space support for arc * add the implementation of syscall * based on 'trap_s' intruction, id = 3 * add the privilege stack * the privilege stack is allocted with thread stack * for the kernel thread, the privilege stack is also a part of thread stack, the start of stack can be configured as stack guard * for the user thread, no stack guard, when the user stack is overflow, it will fall into kernel memory area which requires kernel privilege, privilege violation will be raised * modify the linker template and add MPU_ADDR_ALIGN * add user space corresponding codes in mpu * the user sp aux reg will be part of thread context * When user thread is interruptted for the 1st time, the context is saved in user stack (U bit of IRQ_CTLR is set to 1). When nest interrupt comes, the context is saved in thread's privilege stack * the arc_mpu_regions.c is moved to board folder, as it's board specific * the above codes have been tested through tests/kernel/mem_protect/ userspace for MPU version 2 Signed-off-by: Wayne Ren <wei.ren@synopsys.com>
2018-01-23 17:13:09 +08:00
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
OUTPUT_ARCH(arc)
ENTRY(CONFIG_KERNEL_ENTRY)
MEMORY {
#ifdef FLASH_START
FLASH (rx) : ORIGIN = FLASH_START, LENGTH = FLASH_SIZE
#endif
#ifdef ICCM_START
ICCM (rwx) : ORIGIN = ICCM_START, LENGTH = ICCM_SIZE
#endif
#ifdef SRAM_START
SRAM (rwx) : ORIGIN = SRAM_START, LENGTH = SRAM_SIZE
#endif
#ifdef DCCM_START
DCCM (rw) : ORIGIN = DCCM_START, LENGTH = DCCM_SIZE
#endif
/* Used by and documented in include/linker/intlist.ld */
IDT_LIST (wx) : ORIGIN = 0xFFFFF7FF, LENGTH = 2K
}
SECTIONS {
#include <linker/rel-sections.ld>
GROUP_START(ROMABLE_REGION)
SECTION_PROLOGUE(_TEXT_SECTION_NAME,,ALIGN(1024)) {
_image_rom_start = .;
_image_text_start = .;
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-rom-start.ld>
*(.text .text.*)
*(.gnu.linkonce.t.*)
. = ALIGN(4);
#include <linker/kobject-text.ld>
} GROUP_LINK_IN(ROMABLE_REGION)
CPP: fix static objects init for MWDT toolchain The constructors of static objects are stored in ".ctors" section. In case of MWDT toolchain we have incompatible ".ctors" section format with GNU toolchain. So let's use initialization code provided by MWDT instead of Zephyr one in case of MWDT toolchain usage. As it is done for GNU toolchain We call constructors of static objects but we don't call destructors for them. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Evgeniy Paltsev <PaltsevEvgeniy@gmail.com>
2021-04-26 16:15:49 +03:00
#if defined(CONFIG_CPLUSPLUS) && !defined(CONFIG_CPP_STATIC_INIT_GNU) && defined(__MWDT_LINKER_CMD__)
/* .init section with code iterating over static objects constructors */
SECTION_PROLOGUE(.init,,ALIGN(4)) {
KEEP(*(.init*))
} GROUP_LINK_IN(ROMABLE_REGION)
#endif /* CONFIG_CPLUSPLUS && !CONFIG_CPP_STATIC_INIT_GNU && __MWDT_LINKER_CMD__ */
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
_image_text_end = .;
_image_rodata_start = .;
#include <linker/common-rom.ld>
arc: enable thread local storage This adds the necessary bits to support thread local storage in ARC. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-30 10:21:40 -07:00
#include <linker/thread-local-storage.ld>
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
SECTION_PROLOGUE(_RODATA_SECTION_NAME,,) {
*(".rodata")
*(".rodata.*")
*(.gnu.linkonce.r.*)
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-rodata.ld>
#include <linker/kobject-rom.ld>
CPP: fix static objects init for MWDT toolchain The constructors of static objects are stored in ".ctors" section. In case of MWDT toolchain we have incompatible ".ctors" section format with GNU toolchain. So let's use initialization code provided by MWDT instead of Zephyr one in case of MWDT toolchain usage. As it is done for GNU toolchain We call constructors of static objects but we don't call destructors for them. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Evgeniy Paltsev <PaltsevEvgeniy@gmail.com>
2021-04-26 16:15:49 +03:00
#if defined(CONFIG_CPLUSPLUS) && !defined(CONFIG_CPP_STATIC_INIT_GNU) && defined(__MWDT_LINKER_CMD__)
. = ALIGN(4);
_fctors = .;
KEEP(*(.ctors*))
_ectors = .;
#endif /* CONFIG_CPLUSPLUS && !CONFIG_CPP_STATIC_INIT_GNU && __MWDT_LINKER_CMD__ */
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
} GROUP_LINK_IN(ROMABLE_REGION)
#ifdef __MWDT_LINKER_CMD__
/* TODO: add mwdt specific ROM C++ sections */
#else
#include <linker/cplusplus-rom.ld>
#endif /* __MWDT_LINKER_CMD__ */
_image_rodata_end = .;
MPU_ALIGN(_image_rodata_end - _image_rom_start);
_image_rom_end = .;
_image_rom_size = _image_rom_end - _image_rom_start;
GROUP_END(ROMABLE_REGION)
GROUP_START(RAMABLE_REGION)
#include <app_data_alignment.ld>
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-ram-sections.ld>
#if defined(CONFIG_USERSPACE)
#define APP_SHARED_ALIGN MPU_MIN_SIZE_ALIGN
#define SMEM_PARTITION_ALIGN MPU_ALIGN
#include <app_smem.ld>
_image_ram_start = _app_smem_start;
_app_smem_size = _app_smem_end - _app_smem_start;
_app_smem_rom_start = LOADADDR(_APP_SMEM_SECTION_NAME);
#endif /* CONFIG_USERSPACE */
SECTION_DATA_PROLOGUE(_BSS_SECTION_NAME,(NOLOAD),) {
MPU_MIN_SIZE_ALIGN
/*
* For performance, BSS section is assumed to be 4 byte aligned and
* a multiple of 4 bytes
*/
. = ALIGN(4);
__bss_start = .;
_image_ram_start = .;
__kernel_ram_start = .;
*(".bss")
*(".bss.*")
*(COMMON)
*(".kernel_bss.*")
/*
* BSP clears this memory in words only and doesn't clear any
* potential left over bytes.
*/
__bss_end = ALIGN(4);
} GROUP_DATA_LINK_IN(RAMABLE_REGION, RAMABLE_REGION)
#include <linker/common-noinit.ld>
linker: align __data_ram/rom_start/end linker symbol names Cleanup and preparation commit for linker script generator. Zephyr linker scripts provides start and end symbols for each section, and sometimes even size and LMA start symbols. Generally, start and end symbols uses the following pattern, as: Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end However, this pattern is not followed consistently. To allow for linker script generation and ensure consistent naming of symbols then the following pattern is introduced consistently to allow for cleaner linker script generation. Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end Section size symbol: __foo_size Section LMA start symbol: __foo_load_start This commit aligns the symbols for _data_ram/rom to other symbols and in such a way they follow consistent pattern which allows for linker script and scatter file generation. The symbols are named according to the section name they describe. Section name is `data` A new group named data_region is introduced which instead spans all the input and output sections that was previously covered by __data_ram_start, __data_ram_end, and __data_rom_start. The following symbols are aligned in this commit: - __data_ram_start -> __data_region_start - __data_ram_end -> __data_region_end - __data_rom_start -> __data_region_load_start The following new symbols are introduced so that the data section is aligned with other sections: - __data_end - __data_start value identical to __data_region_start but describes start of the section. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-05-21 21:21:52 +02:00
GROUP_START(DATA_REGION)
__data_region_start = .;
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
SECTION_DATA_PROLOGUE(_DATA_SECTION_NAME,,) {
/* when XIP, .text is in ROM, but vector table must be at start of .data */
linker: align __data_ram/rom_start/end linker symbol names Cleanup and preparation commit for linker script generator. Zephyr linker scripts provides start and end symbols for each section, and sometimes even size and LMA start symbols. Generally, start and end symbols uses the following pattern, as: Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end However, this pattern is not followed consistently. To allow for linker script generation and ensure consistent naming of symbols then the following pattern is introduced consistently to allow for cleaner linker script generation. Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end Section size symbol: __foo_size Section LMA start symbol: __foo_load_start This commit aligns the symbols for _data_ram/rom to other symbols and in such a way they follow consistent pattern which allows for linker script and scatter file generation. The symbols are named according to the section name they describe. Section name is `data` A new group named data_region is introduced which instead spans all the input and output sections that was previously covered by __data_ram_start, __data_ram_end, and __data_rom_start. The following symbols are aligned in this commit: - __data_ram_start -> __data_region_start - __data_ram_end -> __data_region_end - __data_rom_start -> __data_region_load_start The following new symbols are introduced so that the data section is aligned with other sections: - __data_end - __data_start value identical to __data_region_start but describes start of the section. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-05-21 21:21:52 +02:00
__data_start = .;
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
*(".data")
*(".data.*")
*(".kernel.*")
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-rwdata.ld>
linker: align __data_ram/rom_start/end linker symbol names Cleanup and preparation commit for linker script generator. Zephyr linker scripts provides start and end symbols for each section, and sometimes even size and LMA start symbols. Generally, start and end symbols uses the following pattern, as: Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end However, this pattern is not followed consistently. To allow for linker script generation and ensure consistent naming of symbols then the following pattern is introduced consistently to allow for cleaner linker script generation. Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end Section size symbol: __foo_size Section LMA start symbol: __foo_load_start This commit aligns the symbols for _data_ram/rom to other symbols and in such a way they follow consistent pattern which allows for linker script and scatter file generation. The symbols are named according to the section name they describe. Section name is `data` A new group named data_region is introduced which instead spans all the input and output sections that was previously covered by __data_ram_start, __data_ram_end, and __data_rom_start. The following symbols are aligned in this commit: - __data_ram_start -> __data_region_start - __data_ram_end -> __data_region_end - __data_rom_start -> __data_region_load_start The following new symbols are introduced so that the data section is aligned with other sections: - __data_end - __data_start value identical to __data_region_start but describes start of the section. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-05-21 21:21:52 +02:00
__data_end = .;
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: align __data_ram/rom_start/end linker symbol names Cleanup and preparation commit for linker script generator. Zephyr linker scripts provides start and end symbols for each section, and sometimes even size and LMA start symbols. Generally, start and end symbols uses the following pattern, as: Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end However, this pattern is not followed consistently. To allow for linker script generation and ensure consistent naming of symbols then the following pattern is introduced consistently to allow for cleaner linker script generation. Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end Section size symbol: __foo_size Section LMA start symbol: __foo_load_start This commit aligns the symbols for _data_ram/rom to other symbols and in such a way they follow consistent pattern which allows for linker script and scatter file generation. The symbols are named according to the section name they describe. Section name is `data` A new group named data_region is introduced which instead spans all the input and output sections that was previously covered by __data_ram_start, __data_ram_end, and __data_rom_start. The following symbols are aligned in this commit: - __data_ram_start -> __data_region_start - __data_ram_end -> __data_region_end - __data_rom_start -> __data_region_load_start The following new symbols are introduced so that the data section is aligned with other sections: - __data_end - __data_start value identical to __data_region_start but describes start of the section. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-05-21 21:21:52 +02:00
__data_size = __data_end - __data_start;
__data_load_start = LOADADDR(_DATA_SECTION_NAME);
__data_region_load_start = LOADADDR(_DATA_SECTION_NAME);
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
#include <linker/common-ram.ld>
kernel: generate placeholders for kobj tables before final build Due to the use of gperf to generate hash table for kobjects, the addresses of these kobjects cannot change during the last few phases of linking (especially between zephyr_prebuilt.elf and zephyr.elf). Because of this, the gperf generated data needs to be placed at the end of memory to avoid pushing symbols around in memory. This prevents moving these generated blocks to earlier sections, for example, pinned data section needed for demand paging. So create placeholders for use in intermediate linking to reserve space for these generated blocks. Due to uncertainty on the size of these blocks, more space is being reserved which could result in wasted space. Though, this retains the use of hash table for faster lookup. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2021-03-18 14:00:07 -07:00
#include <linker/kobject-data.ld>
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
#ifdef __MWDT_LINKER_CMD__
/* TODO: add mwdt specific RAM C++ sections */
#else
#include <linker/cplusplus-ram.ld>
#endif /* __MWDT_LINKER_CMD__ */
linker: add an initialized DATA_SECTIONS linker location option Current location options for linker source files includes init and noinit ram data, but only a noinit ram section. This makes it impossible for application code to define an initialized RAM output section, such as with the Z_ITERABLE_SECTION_RAM() helpers. Adding a DATA_SECTIONS linker source option for this use case. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2021-08-04 18:21:14 +00:00
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-data-sections.ld>
linker: align __data_ram/rom_start/end linker symbol names Cleanup and preparation commit for linker script generator. Zephyr linker scripts provides start and end symbols for each section, and sometimes even size and LMA start symbols. Generally, start and end symbols uses the following pattern, as: Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end However, this pattern is not followed consistently. To allow for linker script generation and ensure consistent naming of symbols then the following pattern is introduced consistently to allow for cleaner linker script generation. Section name: foo Section start symbol: __foo_start Section end symbol: __foo_end Section size symbol: __foo_size Section LMA start symbol: __foo_load_start This commit aligns the symbols for _data_ram/rom to other symbols and in such a way they follow consistent pattern which allows for linker script and scatter file generation. The symbols are named according to the section name they describe. Section name is `data` A new group named data_region is introduced which instead spans all the input and output sections that was previously covered by __data_ram_start, __data_ram_end, and __data_rom_start. The following symbols are aligned in this commit: - __data_ram_start -> __data_region_start - __data_ram_end -> __data_region_end - __data_rom_start -> __data_region_load_start The following new symbols are introduced so that the data section is aligned with other sections: - __data_end - __data_start value identical to __data_region_start but describes start of the section. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-05-21 21:21:52 +02:00
__data_region_end = .;
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
MPU_MIN_SIZE_ALIGN
/* Define linker symbols */
_image_ram_end = .;
_end = .; /* end of image */
__kernel_ram_end = .;
__kernel_ram_size = __kernel_ram_end - __kernel_ram_start;
ARC: MWDT: workaround for libs with stackcheck As of today we have libraries provided by MWDT build with stackcheck enabled. So we have to provide dummy _fstack, _estack to make it working. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Evgeniy Paltsev <PaltsevEvgeniy@gmail.com>
2021-06-03 14:32:31 +03:00
#ifdef __MWDT_LINKER_CMD__
/* mwdt requires _fstack, _estack which will be used in _stkchk.
* _stkchk is inserted by mwdt automatically, if _fstack, _estack is not
* set correctly, the brk_s instruction will be called
* here, we use a trick to deceive the compiler.
*/
_fstack = _image_ram_start;
_estack = .;
#endif /* __MWDT_LINKER_CMD__ */
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
GROUP_END(RAMABLE_REGION)
/* Located in generated directory. This file is populated by the
* zephyr_linker_sources() Cmake function.
*/
#include <snippets-sections.ld>
#include <linker/debug-sections.ld>
SECTION_PROLOGUE(.ARC.attributes, 0,) {
KEEP(*(.ARC.attributes))
KEEP(*(.gnu.attributes))
}
arc: enable thread local storage This adds the necessary bits to support thread local storage in ARC. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-30 10:21:40 -07:00
/DISCARD/ : {
CPP: fix static objects init for MWDT toolchain The constructors of static objects are stored in ".ctors" section. In case of MWDT toolchain we have incompatible ".ctors" section format with GNU toolchain. So let's use initialization code provided by MWDT instead of Zephyr one in case of MWDT toolchain usage. As it is done for GNU toolchain We call constructors of static objects but we don't call destructors for them. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Evgeniy Paltsev <PaltsevEvgeniy@gmail.com>
2021-04-26 16:15:49 +03:00
#if defined(CONFIG_CPLUSPLUS) && !defined(CONFIG_CPP_STATIC_INIT_GNU) && defined(__MWDT_LINKER_CMD__)
*(.dtors*)
*(.fini*)
*(.eh_frame*)
#endif /* CONFIG_CPLUSPLUS && !CONFIG_CPP_STATIC_INIT_GNU && __MWDT_LINKER_CMD__ */
arc: enable thread local storage This adds the necessary bits to support thread local storage in ARC. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-30 10:21:40 -07:00
*(.note.GNU-stack)
*(.got.plt)
*(.igot.plt)
*(.got)
*(.igot)
}
ARC: linker: merge GNU and MWDT linker scripts As discussed in #22668, there is additional risk ascociated with splitting linker files, as one may update one script and not be aware of the other. Especially related to updating GNU ld, and not mwdt could break code for mwdt unnoticed, as mwdt is not part of CI. Let's create a single entry point for linker template. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-09-15 18:39:35 +03:00
}
Copy permalink