From: Jeff Law <law@redhat.com>
To: Andrew Stubbs <ams@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Document AMD GCN features.
Date: Mon, 21 Jan 2019 18:03:00 -0000 [thread overview]
Message-ID: <b6795ed5-c2cc-4dd5-f9a2-f01a903372c1@redhat.com> (raw)
In-Reply-To: <048fcb30-4c20-6290-64f4-93903df43601@codesourcery.com>
On 1/18/19 4:42 AM, Andrew Stubbs wrote:
> Hi,
>
> This patch adds the documentation needed for the newly-added AMD GCN
> back end.
>
> OK to commit?
>
> Andrew
>
> 190118-gcc-gcn-docs.patch
>
> Document AMD GCN.
>
> 2019-01-18 Andrew Stubbs <ams@codesourcery.com>
>
> gcc/
> * doc/extend.tex (AMD GCN Function Attributes): New section.
> * doc/install.texi (amdgcn-unknown-amdhsa): New instructions.
> * doc/invoke.texi (AMD GCN Options): New section.
> * doc/md.texi (Constraints for Particular Machines): Add AMD GCN.
OK
jeff
next prev parent reply other threads:[~2019-01-21 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:42 Andrew Stubbs
2019-01-21 18:03 ` Jeff Law [this message]
2019-01-22 10:57 ` Andrew Stubbs
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=b6795ed5-c2cc-4dd5-f9a2-f01a903372c1@redhat.com \
--to=law@redhat.com \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
/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).