mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-29 17:26:22 +00:00
4da0f8b796
(OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
44 lines
1.3 KiB
Plaintext
44 lines
1.3 KiB
Plaintext
/*
|
|
* Copyright (c) 2017 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#ifdef CONFIG_USERSPACE
|
|
/* Constraints:
|
|
*
|
|
* - changes to the size of this section between build phases
|
|
* *must not* shift the memory address of any kernel obejcts,
|
|
* since it contains a hashtable of the memory addresses of those
|
|
* kernel objects
|
|
*
|
|
* - It is OK if this section itself is shifted in between builds; for
|
|
* example some arches may precede this section with generated MMU
|
|
* page tables which are also unpredictable in size.
|
|
*
|
|
* The size of the
|
|
* gperf tables is both a function of the number of kernel objects,
|
|
* *and* the specific memory addresses being hashed. It is not something
|
|
* that can be predicted without actually building and compling it.
|
|
*/
|
|
SECTION_DATA_PROLOGUE(kobject_data,,)
|
|
{
|
|
*(".kobject_data.data*")
|
|
|
|
#ifndef LINKER_PASS2
|
|
#ifdef CONFIG_DYNAMIC_OBJECTS
|
|
PROVIDE(_thread_idx_map = .);
|
|
. += CONFIG_MAX_THREAD_BYTES;
|
|
#endif
|
|
#endif
|
|
|
|
/* This is also unpredictable in size, and has the same constraints.
|
|
* On XIP systems this will get put at the very end of ROM.
|
|
*/
|
|
#ifndef CONFIG_XIP
|
|
*(".kobject_data.rodata*")
|
|
#endif
|
|
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
|
|
#endif /* CONFIG_USERSPACE */
|
|
|