public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: "Yangfei (Felix)" <felix.yang@huawei.com>
Cc: Chung-Lin Tang <cltang@codesourcery.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Question about simple_return pattern for the GCC ARM backend.
Date: Mon, 30 Dec 2013 16:48:00 -0000	[thread overview]
Message-ID: <CAJA7tRaojVCHCemHUJeuLzJgmVS+_bdH5Se-cPAY7AOWFHwjOA@mail.gmail.com> (raw)
In-Reply-To: <DA41BE1DDCA941489001C7FBD7A8820E54A334DB@szxema507-mbx.china.huawei.com>

On Mon, Dec 30, 2013 at 3:23 AM, Yangfei (Felix) <felix.yang@huawei.com> wrote:
> Thanks for the reply. I found it in GCC-4.8.
> The gcc version I look at is GCC-4.7. Seems this pattern is not there for this version.

That will be because this was added in time for GCC 4.8. If you need
to find such information as to when something was added please look
into Changelog* files and / or look on the gcc-patches archive. In
this case you need to look for a patch that enables shrink wrapping
for ARM.

Also, checking whether certain features are present or not in the
source tree are best checked in the trunk sources since that is where
new development happens.

Thanks,
Ramana

>
>>
>> On 2013/12/28 09:31 AM, Yangfei (Felix) wrote:
>> > Hi,
>> >
>> >   I think that simple_return standard pattern is useful for the ARM. I mean
>> it should be good for target code performance.
>> >  But seems this pattern is not there for the GCC ARM backend. Can anyone
>> explain the reason why we don’t need this?
>> >
>> > Cheers,
>> > Fei
>> >
>>
>> It does use it. Search for the "<return_str>return" expand pattern, and the
>> "returns" code iterator in config/arm/iterators.md.
>>
>> Chung-Lin
>

      reply	other threads:[~2013-12-30 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  1:31 Yangfei (Felix)
2013-12-28 10:08 ` Chung-Lin Tang
2013-12-30  3:24   ` Yangfei (Felix)
2013-12-30 16:48     ` Ramana Radhakrishnan [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=CAJA7tRaojVCHCemHUJeuLzJgmVS+_bdH5Se-cPAY7AOWFHwjOA@mail.gmail.com \
    --to=ramana.gcc@googlemail.com \
    --cc=cltang@codesourcery.com \
    --cc=felix.yang@huawei.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ramrad01@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).