mirror of
https://github.com/u-boot/u-boot.git
synced 2025-04-16 18:04:48 +00:00
4ee32ea0c4
image_copy_start/end are defined as c variables in order to force the compiler
emit relative references. However, defining those within a section definition
will do the same thing since [0].
So let's remove the special sections from the linker scripts, the
variable definitions from sections.c and define them as a symbols within
a section.
[0] binutils commit 6b3b0ab89663 ("Make linker assigned symbol dynamic only for shared object")
Suggested-by: Sam Edwards <CFSworks@gmail.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Tested-by: Sam Edwards <CFSworks@gmail.com> # Binary output identical
Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
26 lines
1.1 KiB
C
26 lines
1.1 KiB
C
// SPDX-License-Identifier: GPL-2.0+
|
|
/*
|
|
* Copyright 2013 Albert ARIBAUD <albert.u.boot@aribaud.net>
|
|
*/
|
|
#include <linux/compiler.h>
|
|
|
|
/**
|
|
* These two symbols are declared in a C file so that the linker
|
|
* uses R_ARM_RELATIVE relocation, rather than the R_ARM_ABS32 one
|
|
* it would use if the symbols were defined in the linker file.
|
|
* Using only R_ARM_RELATIVE relocation ensures that references to
|
|
* the symbols are correct after as well as before relocation.
|
|
*
|
|
* We need a 0-byte-size type for these symbols, and the compiler
|
|
* does not allow defining objects of C type 'void'. Using an empty
|
|
* struct is allowed by the compiler, but causes gcc versions 4.4 and
|
|
* below to complain about aliasing. Therefore we use the next best
|
|
* thing: zero-sized arrays, which are both 0-byte-size and exempt from
|
|
* aliasing warnings.
|
|
*/
|
|
|
|
char __secure_start[0] __section(".__secure_start");
|
|
char __secure_end[0] __section(".__secure_end");
|
|
char __secure_stack_start[0] __section(".__secure_stack_start");
|
|
char __secure_stack_end[0] __section(".__secure_stack_end");
|
|
char _end[0] __section(".__end");
|