From: "H.J. Lu" <hjl.tools@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] Use Pcrt1.o%s/gPcrt1.o%s for -static-pie
Date: Wed, 01 Nov 2017 16:39:00 -0000 [thread overview]
Message-ID: <CAMe9rOrz1CLPYQQpTVuMondbF8SfZBmezFNPH7xBQqMetssX3Q@mail.gmail.com> (raw)
In-Reply-To: <20171101163221.GA16240@brightrain.aerifal.cx>
On Wed, Nov 1, 2017 at 9:32 AM, Rich Felker <dalias@libc.org> wrote:
> On Sun, Oct 15, 2017 at 06:16:57AM -0700, H.J. Lu wrote:
>> crt1.o is used to create dynamic and non-PIE static executables. Static
>> PIE needs to link with Pcrt1.o, instead of crt1.o, to relocate static PIE
>> at run-time. When -pg is used with -static-pie, gPcrt1.o should be used.
>>
>> Tested on x86-64. OK for master?
>
> Is there a reason you didn't follow the existing naming practice here?
> Openbsd and musl libc have both had static pie for a long time now and
> have used rcrt1.o as the name.
I wasn't aware of rcrt1.o and there is no reference to rcrt1.o in GCC at all.
Does the FSF GCC support static PIE for musl libc? If not, is there a GCC
bug for it?
BTW, I don't mind replacing Pcrt1.o/gPcrt1.o with rcrt1.o/grcrt1.o.
--
H.J.
prev parent reply other threads:[~2017-11-01 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 18:09 H.J. Lu
2017-11-01 16:32 ` Rich Felker
2017-11-01 16:39 ` H.J. Lu [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=CAMe9rOrz1CLPYQQpTVuMondbF8SfZBmezFNPH7xBQqMetssX3Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=dalias@libc.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).