From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: wrong Relocation and not cleared BSS
Date: Sun, 31 Oct 2010 08:43:44 +0100 [thread overview]
Message-ID: <4CCD1E30.6060800@denx.de> (raw)
In-Reply-To: <4CCC18E7.8080708@ahsoftware.de>
Hello Alexander,
Alexander Holler wrote:
> to give the topic a better meaning and to summarize what I think is
> currently happening along with some "pictures" for a better understanding:
>
> We are starting with code (c) and data (d) somewhere in the memory:
>
> ----------
> |cd |
> ----------
>
> The relocation in start.S should achieve this:
>
> ----------
> | cd|
> ----------
Yep, and this works fine on boards, I have access(
arm1136 qong, arm926ejs tx25, suen3 arm926ejs kirkwood,
mx25 magnesium, armv7 omap3_beagle)
> That means code and data should be moved upwards. What
> currently is happening is the following:
>
> ----------
> | d c |
> ----------
really?
I posted you on 27.10.2010 in u-boot%irc.freenode.org (couldn;t
find this in the history :-( ) a log on the tx25, where this works
fine, and we came to the opinion, that you maybe have problems
with your toolchain! IIRC you use gcc-4.5x ... Alexander, did
you tried (as you thought to do) ELDK-4.2 with gcc-4.2.x ?
Are you sure your toolchain works correct with -pie?
> The code is moved upwards, but that code still uses the data at d.
> This results another problem: Some parts in the code are assuming that d
> is cleared (set to zero in start.S). But what start.S does it to clear
> the new location (z in the picture below).
>
> ----------
> | d cz|
> ----------
which is OK.
> Because the code (c) still uses the data (bss) in d and not in z, some
> hard to find errors might occur because the used data isn't set to zero
> as required.
Yep, an that is, what you(we?) have to find out, why this not works
with your toolchain!
> I have almost no knowledge about how gcc and the binutils are handling
> relocation, therfore I can't help much further here. What I think is
> part of the problem, is that -fPIC was removed. Using -pie in LDFLAGS
> might be used to get relocatable code, but the data will not be
> relocated. And I would wonder if that is possible without instructing
> the compiler to build stuff for relocation (-fPIC).
Try to find out, why -pie not works with your tollchain!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2010-10-31 7:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 13:08 [U-Boot] arm: wrong Relocation and not cleared BSS Alexander Holler
2010-10-30 13:36 ` Albert ARIBAUD
2010-10-30 13:45 ` Alexander Holler
2010-10-30 13:57 ` Albert ARIBAUD
2010-10-30 14:07 ` Alexander Holler
2010-10-30 14:39 ` Wolfgang Denk
2010-10-30 16:01 ` Albert ARIBAUD
2010-10-30 16:10 ` Wolfgang Denk
2010-10-30 14:37 ` Wolfgang Denk
2010-10-30 14:36 ` Wolfgang Denk
2010-10-31 10:59 ` Alexander Holler
2010-10-31 11:58 ` Wolfgang Denk
2010-10-31 12:21 ` Albert ARIBAUD
2010-10-31 16:18 ` Alexander Holler
2010-10-30 15:00 ` Wolfgang Denk
2010-10-30 17:21 ` Albert ARIBAUD
2010-10-30 18:01 ` Wolfgang Denk
2010-10-31 7:44 ` Heiko Schocher
2010-10-30 15:15 ` Darius Augulis
2010-10-30 16:44 ` Albert ARIBAUD
2010-10-30 20:03 ` Alexander Holler
2010-10-30 20:51 ` Alexander Holler
2010-10-31 7:47 ` Heiko Schocher
2010-11-02 5:39 ` V, Aneesh
2010-11-02 5:58 ` V, Aneesh
2010-11-02 6:32 ` Albert ARIBAUD
2010-11-02 7:18 ` V, Aneesh
2010-11-02 7:37 ` [U-Boot] Bad page state in process 'swapper' sywang
2010-11-02 7:44 ` Albert ARIBAUD
2010-11-02 8:13 ` sywang
2010-11-02 8:44 ` Wolfgang Denk
2010-11-02 8:40 ` Wolfgang Denk
2010-11-03 2:29 ` sywang
2010-11-02 7:41 ` [U-Boot] arm: wrong Relocation and not cleared BSS Albert ARIBAUD
2010-11-02 8:53 ` V, Aneesh
2010-11-02 9:04 ` Albert ARIBAUD
2010-10-31 7:43 ` Heiko Schocher [this message]
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=4CCD1E30.6060800@denx.de \
--to=hs@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