From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [wwwdocs] gcc-13/changes.html + projects/gomp/: OpenMP update
Date: Mon, 16 Jan 2023 23:16:37 +0100 (CET) [thread overview]
Message-ID: <9fb06c5c-b1aa-5dbf-1865-f6d2a33990b3@pfeifer.com> (raw)
In-Reply-To: <3007e1a3-2840-7847-69f4-d5c951ef1e9e@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hi Tobias,
On Mon, 16 Jan 2023, Tobias Burnus wrote:
>> <code>requires_offload</code>, <code>unified_address</code>
>> - and <code>unified_shared_memory</code> clauses cause that the
>> - only available device is the initial device (the host). Fortran now
>> + and <code>unified_shared_memory</code> clauses imply the initial
>> + device (= the host) as the only available device. Fortran now
> I really stumble over the "as" – that sounds wrong and I fail to parse this
> part.
> I think it should be "is".
happy to make this change. Or do you have an idea to reframe the
sentence (or paragraph) altogether?
(I'm not an expert in that area and so find your description quite
helpful. And based on that "as" -> "is" seems to be sufficient?)
What is your recommendation?
> BTW: Before the release, further updates to changes.html are required.
Keep them coming! :-)
Thanks,
Gerald
next prev parent reply other threads:[~2023-01-16 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 7:37 Tobias Burnus
2022-09-08 15:40 ` Jakub Jelinek
2023-01-14 21:47 ` Gerald Pfeifer
2023-01-16 8:17 ` Tobias Burnus
2023-01-16 22:16 ` Gerald Pfeifer [this message]
2023-01-18 12:39 ` Tobias Burnus
2023-01-20 17:50 ` Jakub Jelinek
2023-01-21 12:48 ` Gerald Pfeifer
2023-01-21 12:53 ` Tobias Burnus
2023-01-23 9:00 ` Tobias Burnus
2023-01-23 9:06 ` Gerald Pfeifer
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=9fb06c5c-b1aa-5dbf-1865-f6d2a33990b3@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tobias@codesourcery.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).