blob: fe6fd73860c559fd12b7546e790e2d589fca36bc [file] [log] [blame]
/* Test linker script for OpenRISC.
Copyright (C) 2017-2021 Free Software Foundation, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <>. */
/* The exception vectors actually start at 0x100, but if you specify
that address here, the "--output-target binary" step will start from
address 0 with the contents meant for address 0x100. */
exception_vectors : ORIGIN = 0 , LENGTH = 8K
ram : ORIGIN = 8K, LENGTH = 2M - 8K
.exception_vectors :
} > exception_vectors
.text :
} > ram
.data :
} > ram
.bss :
/* WARNING about section size alignment:
The start-up assembly code can only clear BSS section sizes
which are aligned to 4 bytes. However, the size of the BSS
section may not be aligned, therefore up to 3 bytes more could
be zeroed on start-up. This is normally not an issue, as the
start of the next section is usually aligned too, so those extra
bytes should be just padding. I did try the following trick to
align the BSS section size, to no avail:
. = ALIGN(., 4);
} > ram
_bss_begin = ADDR(.bss);
_bss_end = _bss_begin + SIZEOF(.bss);
.stack ALIGN(16) (NOLOAD):
} > ram
ENTRY(_start) /* Otherwise, --gc-sections would throw everything away. */