From: Ian Lance Taylor <iant@google.com>
To: "Pan ruochen" <panruochen@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: how to create a self-relocatable raw binary with gcc?
Date: Tue, 12 Aug 2008 14:25:00 -0000 [thread overview]
Message-ID: <m3myjib9sd.fsf@google.com> (raw)
In-Reply-To: <af0faace0808102336r149a2268obea5efcca5a74c54@mail.gmail.com> (Pan ruochen's message of "Mon\, 11 Aug 2008 14\:36\:35 +0800")
"Pan ruochen" <panruochen@gmail.com> writes:
> I want to create a raw binary excutable for MIPS arch, which can relocate
> itself to any load address at runtime without an externel loader.
> How should I compile the sources and write the linker script for this purpose?
There isn't any way to do this without some hacking.
gcc and gas used to support that for the MIPS. The option was
-membedded-pic. It was removed because it stopped working and nobody
was interested in fixing it. So one approach would be to look at old
releases for that code and fix it up.
Ian
prev parent reply other threads:[~2008-08-12 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 16:32 Pan ruochen
2008-08-11 16:47 ` David Daney
2008-08-12 14:25 ` Ian Lance Taylor [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=m3myjib9sd.fsf@google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=panruochen@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).