From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [PATCH][wwwdocs][AArch64] Add entry for target attributes and pragmas
Date: Mon, 07 Sep 2015 12:39:00 -0000 [thread overview]
Message-ID: <55ED8035.9020103@arm.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1509071329180.2597@tuna.site>
Hi Gerald,
On 07/09/15 12:31, Gerald Pfeifer wrote:
> On Wed, 2 Sep 2015, Kyrill Tkachov wrote:
>> My thinking was that when we introduce some new command-line option we
>> list it here and give a short description of it (new -mcpu values, for
>> example). However, here we introduce about 10 new target attributes and
>> pragmas and listing them all would make this entry too long for my
>> liking so as a shorthand for listing them all I chose to point to the
>> documentation.
>>
>> Unless you feel strongly against this reasoning I'd like to commit the
>> patch as is within 48 hours.
> I can follow your reasoning, and anyway the 48 hours are way over ;-),
> just have you considered adding a reference to the documentation (as a
> hyperlink to the respective section, if there is a good one, such as
> https://gcc.gnu.org/onlinedocs/gcc/ARM-Pragmas.html#ARM-Pragmas )?
Good idea, I'll send a patch to mention the link.
The relevant one is:
https://gcc.gnu.org/onlinedocs/gcc/AArch64-Function-Attributes.html#AArch64-Function-Attributes
Thanks,
Kyrill
>
> Gerald
next prev parent reply other threads:[~2015-09-07 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:31 Kyrill Tkachov
2015-09-01 17:29 ` Gerald Pfeifer
2015-09-02 8:25 ` Kyrill Tkachov
2015-09-07 11:32 ` Gerald Pfeifer
2015-09-07 12:39 ` Kyrill Tkachov [this message]
2015-09-14 8:29 ` Kyrill Tkachov
2015-09-14 8:43 ` Gerald Pfeifer
2015-09-15 12:21 ` Christian Bruel
2015-09-15 12:45 ` Kyrill Tkachov
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=55ED8035.9020103@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).