public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sanjeev Premi <premi@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions
Date: Wed,  1 Dec 2010 20:47:14 +0530	[thread overview]
Message-ID: <1291216634-7510-1-git-send-email-premi@ti.com> (raw)

This patch fixes the linker problems noticed while
building the omap3_evm with Codesourcery toolchains
2009q1, 2009q3 and 2010q1.

The compilation was tested as success for both
omap3_evm and omap3_beagle with toolchain versions
2009q1 and 2010q1.

 [1] http://marc.info/?l=u-boot&m=129104332808386&w=2

Signed-off-by: Sanjeev Premi <premi@ti.com>
---
The patch touches all ARMv7 architectures, will need
to be reviewed thoroughly.

I am getting hang of relocation feature, but definitely
hands-on. Impact would have to be reviewd as well.
This is the reason for sending the patch early - before
i start testing on the evm.

 arch/arm/cpu/armv7/u-boot.lds |   26 +++++++++++++++-----------
 1 files changed, 15 insertions(+), 11 deletions(-)

diff --git a/arch/arm/cpu/armv7/u-boot.lds b/arch/arm/cpu/armv7/u-boot.lds
index 5725c30..faf6ad8 100644
--- a/arch/arm/cpu/armv7/u-boot.lds
+++ b/arch/arm/cpu/armv7/u-boot.lds
@@ -55,22 +55,26 @@ SECTIONS
 
 	. = ALIGN(4);
 
-	.rel.dyn : {
-		__rel_dyn_start = .;
-		*(.rel*)
-		__rel_dyn_end = .;
-	}
-
 	.dynsym : {
 		__dynsym_start = .;
 		*(.dynsym)
 	}
 
-	.bss __rel_dyn_start (OVERLAY) : {
-		__bss_start = .;
-		*(.bss)
-		 . = ALIGN(4);
-		_end = .;
+	OVERLAY : NOCROSSREFS
+	{
+		.rel.dyn {
+			__rel_dyn_start = .;
+			*(.rel*)
+			__rel_dyn_end = .;
+		}
+
+		.bss
+		{
+			__bss_start = .;
+			*(.bss)
+			 . = ALIGN(4);
+			_end = .;
+		}
 	}
 
 	/DISCARD/ : { *(.dynstr*) }
-- 
1.7.2.2

             reply	other threads:[~2010-12-01 15:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:17 Sanjeev Premi [this message]
2010-12-01 15:58 ` [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions Premi, Sanjeev
2010-12-01 19:55   ` Wolfgang Denk
2010-12-01 17:13 ` Albert ARIBAUD
2010-12-01 17:19   ` Premi, Sanjeev
2010-12-01 17:32     ` Albert ARIBAUD
2010-12-01 18:19       ` Premi, Sanjeev
2010-12-01 18:36         ` Albert ARIBAUD
2010-12-01 18:54           ` Premi, Sanjeev
2010-12-01 21:39             ` Albert ARIBAUD
2010-12-02  6:59               ` Albert ARIBAUD
2010-12-02  7:34                 ` Wolfgang Denk
2010-12-02  7:51                   ` Albert ARIBAUD
2010-12-02  8:13                     ` Wolfgang Denk
2010-12-02  8:26                       ` Albert ARIBAUD
2010-12-02  8:30                         ` Premi, Sanjeev
2010-12-02  8:42                           ` Albert ARIBAUD
2010-12-02 11:25                             ` Premi, Sanjeev
2010-12-02 11:39                               ` Wolfgang Denk
2010-12-02 12:45                                 ` Premi, Sanjeev
2010-12-02 14:00                                   ` Wolfgang Denk
2010-12-02  8:56                         ` Wolfgang Denk
2010-12-02  8:14                     ` Premi, Sanjeev
2010-12-02  8:18                 ` Premi, Sanjeev
2010-12-01 20:08         ` Wolfgang Denk
2010-12-01 18:23       ` Premi, Sanjeev
2010-12-01 18:28         ` Albert ARIBAUD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1291216634-7510-1-git-send-email-premi@ti.com \
    --to=premi@ti.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox