From: Bernd Schmidt <bschmidt@redhat.com>
To: James Norris <jnorris@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
pault@gcc.gnu.org
Subject: Re: [PATCH] OpenACC documentation for libgomp
Date: Mon, 11 Jan 2016 17:23:00 -0000 [thread overview]
Message-ID: <5693E512.1050406@redhat.com> (raw)
In-Reply-To: <568BE5AF.20109@codesourcery.com>
On 01/05/2016 04:47 PM, James Norris wrote:
> I've updated the original patch after some very helpful
> comments from Sandra (thank you, thank you).
>
> OK to commit to trunk?
I'm probably not fully qualified to review the contents either, but few
people are and it looks reasonable enough that I guess I'll just ack it.
Before that, some questions though:
> +@item @emph{Fortran}:
> +@multitable @columnfractions .20 .80
> +@item @emph{Prototype}: @tab @code{function acc_async_test(arg);}
> +@item @tab @code{integer(kind=acc_handle_kind) arg}
> +@item @tab @code{logical acc_async_test}
> +@end multitable
I guess this is how Fortran functions and their args/return values are
documented? Do we have other examples of this somewhere? I've Cc'ed Paul
Thomas at random as one of the Fortran maintainers for input on whether
this is a good way to document things.
> +about @env{ACC_DEVICE_TYPE} and @env{ACC_DEVICE_NUM} can be found in
> +sections 4.1 and 4.2 of the ââ¬ÅThe OpenACC
> +Application Programming Interfaceââ¬Â, Version 2.0, June, 2013.}.
Non-ascii characters. I'm guessing this should probably be some kind of
texinfo @something{} block; OTOH references to C standards in
standards.texi just name them in plain text.
I wonder if things like OpenMP and OpenACC should be mentioned in
standards.texi, but that is tangential to this patch.
Bernd
next prev parent reply other threads:[~2016-01-11 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 13:30 James Norris
2015-12-18 6:50 ` Sandra Loosemore
2016-01-05 15:48 ` James Norris
2016-01-11 4:10 ` Sandra Loosemore
2016-01-11 17:23 ` Bernd Schmidt [this message]
2016-01-12 15:19 ` James Norris
2016-01-11 17:36 ` Jakub Jelinek
2016-01-12 17:09 ` James Norris
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=5693E512.1050406@redhat.com \
--to=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jnorris@codesourcery.com \
--cc=pault@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).