src/sys/conf/ldscript.arm, branch stable/13 FreeBSD source tree arm: align data section to the supersection. 2024-12-08T13:19:42+00:00 Michal Meloun mmel@FreeBSD.org 2024-11-17T10:50:41+00:00 abed528a9726700303845f5c8b5162fcd32f31dc Offset based data section alignment is probably not applicable to any system other than i386. MFC after: 4 week (cherry picked from commit 60e72eb16a08bdebb40c99cdfcde04e606fe4f3e) 
Offset based data section alignment is probably not applicable to any system
other than i386.

MFC after:	4 week

(cherry picked from commit 60e72eb16a08bdebb40c99cdfcde04e606fe4f3e)
arm: add read_frequently, read_mostly and exclusive_cache_line sections to linker script. 2024-12-08T13:19:42+00:00 Michal Meloun mmel@FreeBSD.org 2024-11-17T10:39:19+00:00 a9956e87506f2c1b99d6fddc60a315e8dc18b55e MFC after: 1 week (cherry picked from commit d98a18d032e6ed3dbae30233d217c6597000e391) 
MFC after:	1 week

(cherry picked from commit d98a18d032e6ed3dbae30233d217c6597000e391)
arm: fix symbols around the .ARM.exidx section 2024-12-08T13:19:42+00:00 Michal Meloun mmel@FreeBSD.org 2024-11-17T10:33:32+00:00 b9d95dc51a21449aa363b3bd963c330ebd690913 Insert a direct assignment to the location counter to ensure that orphaned sections cannot be emitted between the _exidx_start symbol and the .ARM.exidx section. Discussed with: jrtc27 MFC after: 1 week (cherry picked from commit 1701dfae1be3be6f8f1fdd3b6b636d3161b33420) 
Insert a direct assignment to the location counter to ensure that orphaned
sections cannot be emitted between the _exidx_start symbol and the .ARM.exidx
section.

Discussed with:	jrtc27
MFC after:	1 week

(cherry picked from commit 1701dfae1be3be6f8f1fdd3b6b636d3161b33420)
arm: Fix typo in ldscript.arm. 2024-12-08T13:19:42+00:00 Michal Meloun mmel@FreeBSD.org 2024-11-17T10:21:47+00:00 b66e0c51005a0c43c0bd7769cb155b617eb88b1d MFC after: 1 week (cherry picked from commit 0381f0b63b9a5e55d4eca3da5c35ab55e4ce948b) 
MFC after:	1 week

(cherry picked from commit 0381f0b63b9a5e55d4eca3da5c35ab55e4ce948b)
sys: Remove $FreeBSD$: one-line .c comment pattern 2023-08-23T17:43:22+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:15+00:00 4fbf14e22d7b83de7080a8e491ba14a5785a0ff4 Remove /^/[*/]\s*\$FreeBSD\$.*\n/ Similar commit in current: (cherry picked from commit 71625ec9ad2a) 
Remove /^/[*/]\s*\$FreeBSD\$.*\n/

Similar commit in current:
(cherry picked from commit 71625ec9ad2a)
Eliminate the generated ldscript for arm and arm64, and strip $a/$d marker 2019-12-29T18:17:12+00:00 Ian Lepore ian@FreeBSD.org 2019-12-29T18:17:12+00:00 31333ebb9964e2ef53af143498639ec67f4ae40a symbols from the linked kernel. The main thrust of this change is to generate a kernel that has the arm "marker" symbols stripped. Marker symbols start with $a, $d, $t or $x, and are emitted by the compiler to tell other toolchain components about the locations of data embedded in the instruction stream (literal-pool stuff). They are used for generating mixed-endian binaries (which we don't support). The linked kernel has approximately 21,000 such symbols in it, wasting space (500K in kernel.full, 190K in the final linked kernel), and sometimes obscuring function names in stack tracebacks. This change also simplifies the way the kernel is linked. Instead of using sed to generate two different ldscript files to generate both an elf kernel and a binary (elf headers stripped) kernel, we now use a single ldscript that refers to a "text_start" symbol, and we provide the value for that symbol using --defsym on the linker command line. 
symbols from the linked kernel.

The main thrust of this change is to generate a kernel that has the arm
"marker" symbols stripped. Marker symbols start with $a, $d, $t or $x, and
are emitted by the compiler to tell other toolchain components about the
locations of data embedded in the instruction stream (literal-pool
stuff). They are used for generating mixed-endian binaries (which we don't
support). The linked kernel has approximately 21,000 such symbols in it,
wasting space (500K in kernel.full, 190K in the final linked kernel), and
sometimes obscuring function names in stack tracebacks.

This change also simplifies the way the kernel is linked. Instead of using
sed to generate two different ldscript files to generate both an elf kernel
and a binary (elf headers stripped) kernel, we now use a single ldscript
that refers to a "text_start" symbol, and we provide the value for that
symbol using --defsym on the linker command line.
Expose the kernel's build-ID through sysctl 2019-06-04T13:07:10+00:00 Ed Maste emaste@FreeBSD.org 2019-06-04T13:07:10+00:00 74cd06b42ea6f7b46f4782c511757bdfc038d6e8 After our migration (of certain architectures) to lld the kernel is built with a unique build-ID. Make it available via a sysctl and uname(1) to allow the user to identify their running kernel. Submitted by: Ali Mashtizadeh <ali_mashtizadeh.com> MFC after: 2 weeks Relnotes: Yes Event: Waterloo Hackathon 2019 Differential Revision: https://reviews.freebsd.org/D20326 
After our migration (of certain architectures) to lld the kernel is built
with a unique build-ID.  Make it available via a sysctl and uname(1) to
allow the user to identify their running kernel.

Submitted by:	Ali Mashtizadeh <ali_mashtizadeh.com>
MFC after:	2 weeks
Relnotes:	Yes
Event:		Waterloo Hackathon 2019
Differential Revision:	https://reviews.freebsd.org/D20326
remove CONSTRUCTORS from kernel linker scripts 2016-07-28T13:54:46+00:00 Ed Maste emaste@FreeBSD.org 2016-07-28T13:54:46+00:00 45eff3df965297ade6e5781a488d9ede7b87f909 The linker script CONSTRUCTORS keyword is only meaningful "when linking object file formats which do not support arbitrary sections, such as ECOFF and XCOFF"[1] and is ignored for other object file formats. LLVM's lld does not yet accept (and ignore) CONSTRUCTORS, so just remove CONSTRUCTORS from the linker scripts as it has no effect. [1] https://sourceware.org/binutils/docs/ld/Output-Section-Keywords.html Reviewed by: kib Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D7343 
The linker script CONSTRUCTORS keyword is only meaningful "when linking
object file formats which do not support arbitrary sections, such as
ECOFF and XCOFF"[1] and is ignored for other object file formats.

LLVM's lld does not yet accept (and ignore) CONSTRUCTORS, so just remove
CONSTRUCTORS from the linker scripts as it has no effect.

[1] https://sourceware.org/binutils/docs/ld/Output-Section-Keywords.html

Reviewed by:	kib
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D7343
Remove STARTUP_PAGETABLE_ADDR from the ARM configs and replace it with 2014-01-28T09:12:04+00:00 Andrew Turner andrew@FreeBSD.org 2014-01-28T09:12:04+00:00 979d76c94876df7d7b10c79d1b3c33b04143eb70 memory at the end of the kernel. This helps reduce the SoC and board specific configuration required. Reviewed by: bsdimp Tested by: jmg (armeb), br 
memory at the end of the kernel.

This helps reduce the SoC and board specific configuration required.

Reviewed by:	bsdimp
Tested by:	jmg (armeb), br
Correctly align the unwind tables. Without this clang may incorrectly align 2013-03-10T00:47:19+00:00 Andrew Turner andrew@FreeBSD.org 2013-03-10T00:47:19+00:00 67727fbfceb0eb6d48c14919a702064b507a7cdf them causing an alignment fault when producing a backtrace. 
them causing an alignment fault when producing a backtrace.