diff options
| author | Wolfgang Denk <wd@denx.de> | 2008-01-12 20:31:39 +0100 |
|---|---|---|
| committer | Wolfgang Denk <wd@denx.de> | 2008-01-12 20:31:39 +0100 |
| commit | 64134f011254123618798ff77c42ba196b2ec485 (patch) | |
| tree | da048d328c9cb0bd00a89bb066d2e75cd5a52fb1 /board/esd/tasreg/u-boot.lds | |
| parent | 3afac79ec27b91df185f090b31dad9620779f440 (diff) | |
| download | u-boot-imx-64134f011254123618798ff77c42ba196b2ec485.zip u-boot-imx-64134f011254123618798ff77c42ba196b2ec485.tar.gz u-boot-imx-64134f011254123618798ff77c42ba196b2ec485.tar.bz2 | |
Fix linker scripts: add NOLOAD atribute to .bss/.sbss sections
With recent toolchain versions, some boards would not build because
or errors like this one (here for ocotea board when building with
ELDK 4.2 beta):
ppc_4xx-ld: section .bootpg [fffff000 -> fffff23b] overlaps section .bss [fffee900 -> fffff8ab]
For many boards, the .bss section is big enough that it wraps around
at the end of the address space (0xFFFFFFFF), so the problem will not
be visible unless you use a 64 bit tool chain for development. On
some boards however, changes to the code size (due to different
optimizations) we bail out with section overlaps like above.
The fix is to add the NOLOAD attribute to the .bss and .sbss
sections, telling the linker that .bss does not consume any space in
the image.
Signed-off-by: Wolfgang Denk <wd@denx.de>
Diffstat (limited to 'board/esd/tasreg/u-boot.lds')
| -rw-r--r-- | board/esd/tasreg/u-boot.lds | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/board/esd/tasreg/u-boot.lds b/board/esd/tasreg/u-boot.lds index a803b1c..4f47323 100644 --- a/board/esd/tasreg/u-boot.lds +++ b/board/esd/tasreg/u-boot.lds @@ -131,7 +131,7 @@ SECTIONS __init_end = .; __bss_start = .; - .bss : + .bss (NOLOAD) : { _sbss = .; *(.sbss) *(.scommon) |