All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain	versions
Date: Wed, 01 Dec 2010 22:39:38 +0100	[thread overview]
Message-ID: <4CF6C09A.7050206@free.fr> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247AFDAD9@dbde02.ent.ti.com>

This one is a conundrum.

Using 2010q1, building omap3_evm causes a linker warning 
"arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x8003e8f0 overlaps 
previous sections" while building omap3_beagle does not cause any linker 
warning.

Both boards use the same armv7 u-boot.lds and have a .bss which is way 
bigger than the .rel.dyn plus .dynsym sections that it does overlay. 
IOW, they have a similar layout for .rel.dyn, .dynsym and .bss, but one 
gets the warning and one does not.

The one difference a readelf shows is that for beagle, there is only one 
segment:

00  .text .rodata .hash .data .got.plt .u_boot_cmd .rel.dyn .dynsym

While for evm there is

00  .text .rodata .hash .data .got.plt .u_boot_cmd .rel.dyn .bss
01  .dynsym

Note that .bss has appeared in segment 00 for evm, whereas it was absent 
for beagle, and that .dynsym was rejected to a second segment -- why? I 
don't know.

Note: I've tried with putting input sections .rel.dyn and .dynsym into a 
single output section .rel.dyn: this makes the second segment disappear, 
but for evm the warning remains and .bss remains in the segment.

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-12-01 21:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:17 [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions Sanjeev Premi
2010-12-01 15:58 ` 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 [this message]
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=4CF6C09A.7050206@free.fr \
    --to=albert.aribaud@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.