public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Graeme Russ <gruss@tss-engineering.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Let's bury CONFIG_NEEDS_MANUAL_RELOC
Date: Wed, 04 Feb 2015 23:16:41 +1100	[thread overview]
Message-ID: <54D20DA9.9010304@tss-engineering.com> (raw)
In-Reply-To: <20150204112952.2ba1e086@lilith>

Hi Albert,

On 04/02/15 21:29, Albert ARIBAUD wrote:
> Hello Graeme,
>
> On Wed, 04 Feb 2015 18:14:22 +1100, Graeme Russ
> <gruss@tss-engineering.com> wrote:


>> So the first question that we need to answer is: Do the avr32, m68k,
>> nds32, and sparc toolchains support the generation of the relevant
>> sections needed to perform relocation in a manner similar to x86 (i.e
>> generation of relocation references into sections of the final U-Boot
>> binary)?
>
> Those arches which use GCC should be able to use -pie / -pic-executable
> and possibly --emit-relocs, as none of these is arch-specific.

That was my understanding too - it's a function of ELF, not the 
architecture.

> Then, each arch might have to look into what GCC options are needed.
> For the record, on ARM, I did not need any gcc option, but actually
> had one -fPIC option /removed/.

Yes, I vaguely remember this. The difference is that -fPIC is used for 
relocatable LIBRARIES whereas -fPIE is used for relocatable EXECUTABLES. 
Since U-Boot is a monolithic executable, -fPIC makes no sense

Regards,


Graeme

      reply	other threads:[~2015-02-04 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  7:14 [U-Boot] Let's bury CONFIG_NEEDS_MANUAL_RELOC Graeme Russ
2015-02-04 10:29 ` Albert ARIBAUD
2015-02-04 12:16   ` Graeme Russ [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=54D20DA9.9010304@tss-engineering.com \
    --to=gruss@tss-engineering.com \
    --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