public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <Tobias_Burnus@mentor.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Tobias Burnus <tobias@codesourcery.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs][Patch] Add OpenMP by-GCC-version implementation status
Date: Sat, 21 Jan 2023 21:57:17 +0100 (CET)	[thread overview]
Message-ID: <5096c5f4-e8e2-aca5-1cdb-145284ebfad9@pfeifer.com> (raw)
In-Reply-To: <3f8d27e6-0f92-95a9-6d1f-0ce08fb4f13a@mentor.com>

On Tue, 17 May 2022, Tobias Burnus wrote:
> Done so: https://gcc.gnu.org/projects/gomp/

Nice!

> Thanks again for all the comments!

Always welcome! One detailed I noticed only now:

   The GOMP project consists of implementation of OpenMP and OpenACC to 
   permit annotating the source code to permit running it concurrently
   ^^^^^^                               ^^^^^^
   with thread parallelization and on offloading devices

Do you have a good idea how to reword that to avoid two instances of 
"permit" in the same sentence, so close to each other?

Gerald

  parent reply	other threads:[~2023-01-21 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 21:27 Tobias Burnus
2022-05-16  9:42 ` Tobias Burnus
2022-05-17  7:54   ` Gerald Pfeifer
2022-05-17  8:21   ` Jakub Jelinek
2022-05-17  8:49     ` Tobias Burnus
2022-05-17  9:00       ` Jakub Jelinek
2022-05-17  9:50         ` Tobias Burnus
2022-05-17 10:02           ` Jakub Jelinek
2023-01-21 20:57           ` Gerald Pfeifer [this message]
2022-05-16 10: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=5096c5f4-e8e2-aca5-1cdb-145284ebfad9@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=Tobias_Burnus@mentor.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).