From: "H. Peter Anvin" <hpa@zytor.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, Jiri Kosina <jkosina@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Josh Boyer <jwboyer@redhat.com>
Subject: Re: RFC: binutils PATCH: Set e_type to ET_EXEC for -pie -Ttext-segment=
Date: Tue, 10 Dec 2013 11:08:20 -0800 [thread overview]
Message-ID: <52A766A4.7040202@zytor.com> (raw)
In-Reply-To: <CAMe9rOrKGSxr9X5txGq2Js0vGwXdwxPT+ip70-YZs-Wz-aPgQg@mail.gmail.com>
On 12/10/2013 04:20 AM, H.J. Lu wrote:
> On Mon, Dec 9, 2013 at 8:57 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Where do the _32 and _32S relocations come from? Are we mixing multiple things inside -pie?
>
> They come from crt1.o and crtbegin.o. -pie uses Scrt1.o and crtbeginS.o.
>
OK, so this is fundamentally an issue with the gcc wrapper... there
isn't a way to get the relocatable crt files without telling the linker
to link PIE (except perhaps using some -Wl option, maybe "-Wl,-no-pie"?)
Either way, if the *only* goal is to get the file above a certain point,
like 4 GiB, then there is no reason not to randomize upward.
-hpa
next prev parent reply other threads:[~2013-12-10 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 12:20 RFC: binutils PATCH: Set e_type to ET_EXEC for -pie -Ttext-segment= H.J. Lu
2013-12-10 19:08 ` H. Peter Anvin [this message]
2013-12-10 19:15 ` H.J. Lu
2013-12-10 19:26 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 3:10 H.J. Lu
2013-12-10 22:36 ` Alan Modra
2013-12-10 22:47 ` H.J. Lu
2013-12-12 15:42 ` H.J. Lu
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=52A766A4.7040202@zytor.com \
--to=hpa@zytor.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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.