From: Andrew Stubbs <ams@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>,
Jakub Jelinek <jakub@redhat.com>,
Andrew Stubbs <andrew_stubbs@mentor.com>
Subject: Re: [wwwdocs] gcc-12/changes.html: OpenMP + GCN update
Date: Wed, 23 Jun 2021 10:58:53 +0100 [thread overview]
Message-ID: <f5f2debe-1c80-73de-2f67-a67620114b7e@codesourcery.com> (raw)
In-Reply-To: <c6e01061-6df1-d699-eb1e-4cc816d33f14@codesourcery.com>
On 23/06/2021 10:53, Tobias Burnus wrote:
> + additionally the following features which were available in C and C++
> + before: <code>depobj</code>, <code>mutexinoutset</code> and
I realise that you did not invent this awkward wording, but I'd prefer ...
"the following features that were previously only available in C and
C++: ...."
Andrew
next prev parent reply other threads:[~2021-06-23 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:53 Tobias Burnus
2021-06-23 9:58 ` Andrew Stubbs [this message]
2021-06-28 9:47 ` Tobias Burnus
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=f5f2debe-1c80-73de-2f67-a67620114b7e@codesourcery.com \
--to=ams@codesourcery.com \
--cc=andrew_stubbs@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).