public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions
Date: Wed, 01 Dec 2010 21:08:57 +0100	[thread overview]
Message-ID: <20101201200857.7C93D134FEF@gemini.denx.de> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247AFDACE@dbde02.ent.ti.com>

Dear "Premi, Sanjeev",

In message <B85A65D85D7EB246BE421B3FB0FBB5930247AFDACE@dbde02.ent.ti.com> you wrote:
>
>      1) why the current metod produces different errors across
>         different toolchain versions.

Different tool chains may prvide different quality of optimizations
(and bugs), resulting in differnt variable locations. With one memory
map you notice immediately if a value gets overwritten, with another
you may not notice it.

>      2) How does presence of one variable alone breaks the build?

It changes the memory map, and thus the location which may get
overwritten.

>         At least, compiler doesn't complain. Even moving it out

How should it? From the tool chain's point of view everything is fine.
It's the programmer who did things that lead to trouble; we only get
what we deserve.

>         of .bss by explicit initialization doesn't help.

How exactly did you initialize the variable? Like "int foo = 0;"?
Note that this will still go to BSS. 


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Harrison's Postulate:
	For every action, there is an equal and opposite criticism.

  parent reply	other threads:[~2010-12-01 20:08 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
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 [this message]
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=20101201200857.7C93D134FEF@gemini.denx.de \
    --to=wd@denx.de \
    --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