All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth@southpole.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Fixup entries
Date: Mon, 14 Apr 2008 21:08:41 +0200	[thread overview]
Message-ID: <1208200121.7466.43.camel@localhost.localdomain> (raw)
In-Reply-To: <009e01c89a95$ebd30960$c3791c20$@Tjernlund@transmode.se>


On Thu, 2008-04-10 at 01:03 +0200, Joakim Tjernlund wrote:
> > -----Original Message-----
> > From: kenneth johansson [mailto:kenneth at southpole.se]
> > I had this misconception that the GOT was all that was needed for
> > relocation.
> > Could not find any useful information on what rules apply to gcc and
> > binutils for handling stuff in this fixup section.
> > 
> > Anybody have any information on this?
> 
> Nope, never found anything either. To see a working one in u-boot, look at
> mpc83xx start.S and its linker scripts.
> 
>  Jocke
> 
> 

Found some code from gcc that do the relocation in the same way we want
in u-boot. 

http://gcc.gnu.org/viewcvs/trunk/gcc/config/rs6000/eabi.asm?revision=130805&view=markup

I tried to call __eabi and link with libgcc plus ecrti.o, ecrtn.o  but
in the end I had one silly undefined symbol(.Lfini) that I could not get
past the linker. 

But I think copying that code over into u-boot could not hurt. And
considering the age of that code I can't imagine that anybody has a tool
chain that can't handle using the -mrelocatable. It would be nice to
remove the manual relocation done when it's not needed it is just
confusing.

      parent reply	other threads:[~2008-04-14 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  9:32 [U-Boot-Users] Fixup entries Kenneth Johansson
2008-04-09 11:23 ` Joakim Tjernlund
2008-04-09 14:46   ` Kenneth Johansson
2008-04-09 16:19     ` Joakim Tjernlund
2008-04-09 23:00       ` kenneth johansson
2008-04-09 23:03         ` Joakim Tjernlund
2008-04-09 23:52           ` kenneth johansson
2008-04-14 19:08           ` Kenneth Johansson [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=1208200121.7466.43.camel@localhost.localdomain \
    --to=kenneth@southpole.se \
    --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.