public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>
Cc: Jeff Law <law@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>,
	       Jiong Wang <jiong.wang@foss.arm.com>,
	       Bernd Schmidt <bschmidt@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>,
	       Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: PING: [PATCH] PR target/67215: -fno-plt needs improvements for x86
Date: Wed, 28 Oct 2015 11:05:00 -0000	[thread overview]
Message-ID: <20151028110332.GA13132@arm.com> (raw)
In-Reply-To: <20151028110114.GA13365@arm.com>

On Wed, Oct 28, 2015 at 11:01:15AM +0000, James Greenhalgh wrote:
> On Wed, Oct 28, 2015 at 10:13:07AM +0000, Ramana Radhakrishnan wrote:
> > 
> > 
> > On 27/10/15 20:57, Jeff Law wrote:
> > >> a
> > >>
> > >> * config/aarch64/aarch64.md (call, call_value): Handle noplt.
> > > FWIW -ENOPATCH.
> > > 
> > > jeff
> > 
> > 
> > Bah - finger trouble. Sorry about that. Here it is and also handling sibcall
> > patterns. Tested aarch64-none-elf with no regressions.
> 
> 
>     if (!REG_P (callee)
>        && ((GET_CODE (callee) != SYMBOL_REF)
> 	   || && aarch64_is_noplt_call_p (callee)))
> 
> ???

This thread seems destined to cause typos and finger slips...

     if (!REG_P (callee)
        && ((GET_CODE (callee) != SYMBOL_REF)
 	     || aarch64_is_noplt_call_p (callee)))

Obviously :).

Thanks,
James

  reply	other threads:[~2015-10-28 11:03 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
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 [this message]
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=20151028110332.GA13132@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jiong.wang@foss.arm.com \
    --cc=law@redhat.com \
    --cc=ramana.radhakrishnan@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).