From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jiong Wang <jiong.wang@foss.arm.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING: [PATCH] PR target/67215: -fno-plt needs improvements for x86
Date: Tue, 27 Oct 2015 13:07:00 -0000 [thread overview]
Message-ID: <CAMe9rOrL89kK=qxPS7n4e28+-3cpv_EdG0E0YT5uf3ppYNFamw@mail.gmail.com> (raw)
In-Reply-To: <562F739F.2090000@foss.arm.com>
On Tue, Oct 27, 2015 at 5:52 AM, Jiong Wang <jiong.wang@foss.arm.com> wrote:
>
>
> On 27/10/15 11:37, H.J. Lu wrote:
>>
>> On Tue, Oct 27, 2015 at 4:20 AM, Bernd Schmidt <bschmidt@redhat.com>
>> wrote:
>>>
>>> On 10/19/2015 09:55 PM, H.J. Lu wrote:
>>>>
>>>> * calls.c (prepare_call_address): Don't handle -fno-plt here.
>>>
>>>
>>> Is any other target using -fno-plt? If not, and if that's really just a
>>
>> aarch64 is the only target which checks -fno-plt from commit log below.
>> I CCed the code author. aarch64 may suffer from the same issue.
>
>
> H.J,
>
> Thanks for the info.
>
> After a quick reading of the PR at
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67215,
> I found the problem description is very x86 specific, I still don't
> understand what's
> wrong if we do the following transformation when -fno-plt specified on
> x86-74, thus I
> am not sure whether there is problem exist on aarch64. Can you please give
> more explanation?
>
> call proc2@PLT
>
> ||
> V
>
> movq proc2@GOTPCREL(%rip), %rax
> call *%rax
call *proc2@GOTPCREL(%rip)
doesn't use a register and saves one instruction.
--
H.J.
next prev parent reply other threads:[~2015-10-27 13:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:59 H.J. Lu
2015-10-27 11:28 ` Bernd Schmidt
2015-10-27 11:38 ` H.J. Lu
2015-10-27 12:52 ` Uros Bizjak
2015-10-27 12:57 ` Jiong Wang
2015-10-27 13:07 ` H.J. Lu [this message]
2015-10-27 13:55 ` Jiong Wang
2015-10-27 14:49 ` Ramana Radhakrishnan
2015-10-27 15:20 ` H.J. Lu
2015-10-27 15:27 ` Jiong Wang
2015-10-27 15:33 ` H.J. Lu
2015-10-27 17:53 ` Jeff Law
2015-10-27 15:45 ` Ramana Radhakrishnan
2015-10-27 17:50 ` Jeff Law
2015-10-27 19:31 ` H.J. Lu
2015-10-29 1:10 ` Jeff Law
2015-10-29 1:11 ` H.J. Lu
2015-10-29 1:14 ` Bernd Schmidt
2015-10-29 1:21 ` H.J. Lu
2015-10-29 1:47 ` Bernd Schmidt
2015-10-29 3:39 ` H.J. Lu
2015-10-29 9:46 ` Ramana Radhakrishnan
2015-10-29 17:18 ` Jeff Law
2015-10-29 17:15 ` Jeff Law
2015-12-01 13:38 ` David Edelsohn
2015-10-29 17:08 ` Jeff Law
2015-10-27 21:02 ` Jeff Law
2015-10-28 10:36 ` Ramana Radhakrishnan
2015-10-28 11:01 ` James Greenhalgh
2015-10-28 11:05 ` James Greenhalgh
2015-10-28 14:45 ` Ramana Radhakrishnan
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='CAMe9rOrL89kK=qxPS7n4e28+-3cpv_EdG0E0YT5uf3ppYNFamw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@foss.arm.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).