From: Sandra Loosemore <sandra@codesourcery.com>
To: "Yangfei (Felix)" <felix.yang@huawei.com>
Cc: "richard.earnshaw@arm.com" <richard.earnshaw@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jiangjiji <jiangjiji@huawei.com>
Subject: Re: [PING, AArch64] Add long-call attribute and pragma interfaces
Date: Fri, 03 Apr 2015 19:12:00 -0000 [thread overview]
Message-ID: <551EE5D8.1000701@codesourcery.com> (raw)
In-Reply-To: <DA41BE1DDCA941489001C7FBD7A8820E837D8853@szxema507-mbx.china.huawei.com>
On 04/02/2015 11:59 PM, Yangfei (Felix) wrote:
> Patch ping: https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01148.html
This patch needs documentation for the new attributes and pragmas before
it can be committed. (Since this is a new feature I think it has to
wait until stage 1, too, but that's not my call.)
-Sandra
next prev parent reply other threads:[~2015-04-03 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 6:00 Yangfei (Felix)
2015-04-03 19:12 ` Sandra Loosemore [this message]
2015-04-13 1:33 ` Yangfei (Felix)
2015-05-05 11:50 ` [PING^2, " Yangfei (Felix)
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=551EE5D8.1000701@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=felix.yang@huawei.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiangjiji@huawei.com \
--cc=richard.earnshaw@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).