From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Sriraman Tallam <tmsriram@google.com>
Subject: Re: [PATCH x86_64] Optimize access to globals in "-fpie -pie" builds with copy relocations
Date: Tue, 02 Dec 2014 22:14:00 -0000 [thread overview]
Message-ID: <CAMe9rOqrcu_JdzA3hKNHjEV3Vyt9wJ3dXb6JXfPWmiVqpMMzsg@mail.gmail.com> (raw)
In-Reply-To: <20141202201929.GN1860@tucnak.redhat.com>
On Tue, Dec 2, 2014 at 12:19 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Tue, Dec 02, 2014 at 12:16:09PM -0800, H.J. Lu wrote:
>> > IMO, nobody will use this highly special x86_64-only option. It would
>> > be best for gnu-ld to reach feature parity with gold as far as this
>> > functionality is concerned. In this case, the optimization would be
>> > auto-configured, and would fire automatically, without any user
>> > intervention.
>>
>> I will implement it in ld after its support is checked into GCC.
>
> I think it would be better to do it the other way around, so that gcc can be
> configured against the right ld from the start.
>
Consider it is done. I will check it into binutils ths week.
--
H.J.
next prev parent reply other threads:[~2014-12-02 22:14 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 19:19 Uros Bizjak
2014-12-02 19:39 ` H.J. Lu
2014-12-02 19:40 ` H.J. Lu
2014-12-02 20:01 ` Uros Bizjak
2014-12-02 20:43 ` H.J. Lu
2014-12-02 20:19 ` Jakub Jelinek
2014-12-02 22:14 ` H.J. Lu [this message]
2014-12-02 23:21 ` H.J. Lu
2014-12-03 13:47 ` H.J. Lu
2014-12-03 15:01 ` H.J. Lu
2014-12-03 21:35 ` H.J. Lu
2014-12-04 12:44 ` Uros Bizjak
2014-12-04 16:46 ` H.J. Lu
2014-12-04 19:32 ` Uros Bizjak
2015-02-03 19:25 ` Sriraman Tallam
2015-02-03 19:26 ` Sriraman Tallam
2015-02-03 19:36 ` Jakub Jelinek
2015-02-03 21:20 ` Sriraman Tallam
2015-02-03 21:29 ` H.J. Lu
2015-02-03 21:36 ` Sriraman Tallam
2015-02-03 22:03 ` H.J. Lu
2015-02-03 22:19 ` Jakub Jelinek
2015-02-04 1:16 ` H.J. Lu
2015-02-04 18:27 ` Sriraman Tallam
2015-02-04 18:31 ` Jakub Jelinek
2015-02-04 18:38 ` H.J. Lu
2015-02-04 18:42 ` Jakub Jelinek
2015-02-04 18:45 ` H.J. Lu
2015-02-04 18:51 ` Sriraman Tallam
2015-02-04 18:57 ` H.J. Lu
2015-02-04 21:53 ` Sriraman Tallam
2015-02-04 22:37 ` H.J. Lu
2015-02-04 22:47 ` Bernhard Reutner-Fischer
2015-02-04 23:10 ` H.J. Lu
2015-02-04 23:29 ` H.J. Lu
2015-02-05 16:57 ` Bernhard Reutner-Fischer
2015-02-05 18:54 ` Richard Henderson
2015-02-05 19:01 ` H.J. Lu
2015-02-05 19:59 ` Richard Henderson
2015-02-05 22:05 ` Sriraman Tallam
2015-02-05 22:47 ` H.J. Lu
2015-02-05 22:48 ` Sriraman Tallam
2015-02-06 16:25 ` H.J. Lu
2015-02-27 23:39 ` H.J. Lu
2015-02-27 23:46 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2014-12-04 22:19 Dominique Dhumieres
2014-12-04 23:54 ` H.J. Lu
2014-05-15 18:34 Sriraman Tallam
2014-05-19 18:11 ` Sriraman Tallam
2014-06-09 22:55 ` Sriraman Tallam
2014-06-21 0:17 ` Sriraman Tallam
2014-06-26 17:55 ` Sriraman Tallam
2014-07-11 17:42 ` Sriraman Tallam
2014-09-02 18:15 ` Sriraman Tallam
2014-09-02 20:40 ` Richard Henderson
2014-09-03 7:25 ` Bernhard Reutner-Fischer
2014-09-08 22:19 ` Sriraman Tallam
2014-09-19 21:11 ` Sriraman Tallam
2014-09-29 17:57 ` Sriraman Tallam
2014-10-06 20:43 ` Sriraman Tallam
2014-11-10 23:35 ` Sriraman Tallam
2014-12-02 18:01 ` Sriraman Tallam
2014-12-02 19:06 ` 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=CAMe9rOqrcu_JdzA3hKNHjEV3Vyt9wJ3dXb6JXfPWmiVqpMMzsg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tmsriram@google.com \
--cc=ubizjak@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).