summaryrefslogtreecommitdiffstats
path: root/board/psyent/pk1c20
diff options
context:
space:
mode:
authorWolfgang Denk <wd@denx.de>2008-01-12 20:31:39 +0100
committerWolfgang Denk <wd@denx.de>2008-01-12 20:31:39 +0100
commit64134f011254123618798ff77c42ba196b2ec485 (patch)
treeda048d328c9cb0bd00a89bb066d2e75cd5a52fb1 /board/psyent/pk1c20
parent3afac79ec27b91df185f090b31dad9620779f440 (diff)
downloadblackbird-obmc-uboot-64134f011254123618798ff77c42ba196b2ec485.tar.gz
blackbird-obmc-uboot-64134f011254123618798ff77c42ba196b2ec485.zip
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/psyent/pk1c20')
-rw-r--r--board/psyent/pk1c20/u-boot.lds4
1 files changed, 2 insertions, 2 deletions
diff --git a/board/psyent/pk1c20/u-boot.lds b/board/psyent/pk1c20/u-boot.lds
index 8f9cd8fa59..d3b7c31ae9 100644
--- a/board/psyent/pk1c20/u-boot.lds
+++ b/board/psyent/pk1c20/u-boot.lds
@@ -88,7 +88,7 @@ SECTIONS
* bss follows. We keep it adjacent to simplify init code.
*/
__bss_start = .;
- .sbss :
+ .sbss (NOLOAD) :
{
*(.sbss)
*(.sbss.*)
@@ -96,7 +96,7 @@ SECTIONS
*(.scommon)
}
. = ALIGN(4);
- .bss :
+ .bss (NOLOAD) :
{
*(.bss)
*(.bss.*)
OpenPOWER on IntegriCloud