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] Build failures with older toolchain
Date: Wed, 01 Dec 2010 16:02:34 +0100	[thread overview]
Message-ID: <4CF6638A.3050506@free.fr> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247AFDA2E@dbde02.ent.ti.com>

Le 01/12/2010 15:56, Premi, Sanjeev a ?crit :

> When everything failed, I went back to the u-boot.lds and
> changed the way overlay is defined.
>
> ...AND PROBLEM SEEMS TO BE SOLVED!

This most probably means some of the code running before relocation uses 
BSS; see below.

> I can now compile u-boot with both 2009q1 and 2010q1 without
> any error. (yet to try with 2010.09)
>
> To verify, I wanted to do a before-and-after comparison but
> couldn't have done for the omap3_evm - used omap3_beagle instead.
>
> I haven't yet tried running the binary on the board; but here
> are top level observations:
>
> 1) .bss and .rel.dyn are starting at same address.

This is normal and should not have any negative impact as long as code 
that runs before relocation does not access BSS -- and it should not, 
since BSS only exists after relocation.

> 2) The size of .rodata has increased. (Why? not yet spent time on?)

Weird. Can you provide all necessary info for duplicating these two builds?

> Sending the patch in next few mins:

If that's a patch to remove the overlay in the .lds, it's a Nak from me 
already.

> ~sanjeev

Amicalement,
-- 
Albert.

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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 18:50 [U-Boot] Build failures with older toolchain Premi, Sanjeev
2010-11-19 19:43 ` Premi, Sanjeev
2010-11-19 20:13   ` Wolfgang Denk
2010-11-22  9:14     ` Premi, Sanjeev
2010-11-22 13:50       ` Premi, Sanjeev
2010-11-22 14:31         ` Albert ARIBAUD
2010-11-22 14:42           ` Premi, Sanjeev
2010-11-22 15:02           ` Premi, Sanjeev
2010-11-22 15:23             ` Albert ARIBAUD
2010-11-22 15:27               ` Premi, Sanjeev
2010-11-22 15:35                 ` Albert ARIBAUD
2010-11-29  9:47                 ` Premi, Sanjeev
2010-11-29 10:32                   ` Albert ARIBAUD
2010-11-29 10:37                     ` Premi, Sanjeev
2010-11-29 11:29                       ` Wolfgang Denk
2010-11-29 11:48                         ` Premi, Sanjeev
2010-11-29 12:05                           ` Wolfgang Denk
2010-11-29 15:08                             ` Premi, Sanjeev
2010-11-29 15:33                               ` Albert ARIBAUD
2010-11-29 15:39                                 ` Premi, Sanjeev
2010-11-30 14:25                               ` Premi, Sanjeev
2010-11-30 16:44                                 ` Dirk Behme
2010-11-30 18:23                                   ` Premi, Sanjeev
2010-12-01 14:56                                 ` Premi, Sanjeev
2010-12-01 15:02                                   ` Albert ARIBAUD [this message]
2010-12-01 15:18                                     ` Premi, Sanjeev
2010-11-29 10:35                   ` Wolfgang Denk
2010-11-29 10:44                     ` Premi, Sanjeev

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=4CF6638A.3050506@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.