public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs][Patch] Add OpenMP by-GCC-version implementation status
Date: Tue, 17 May 2022 11:00:29 +0200	[thread overview]
Message-ID: <YoNkLTpkpGRvtiUO@tucnak> (raw)
In-Reply-To: <d9a57d28-67a1-9fa8-d67e-49f490cf68e7@codesourcery.com>

On Tue, May 17, 2022 at 10:49:42AM +0200, Tobias Burnus wrote:
> Thoughts on this part?

Either place is fine.

> > > +<tr><td>Map-order clarifications</td><td>GCC?</td><td></td></tr>
> > This entry I gave up on, it isn't exactly clear to me what that
> > bullet is about and once we figure that out, we need to do some archeology
> > on whether we support it at all and if yes, since which commit and thus
> > since which GCC version.
> I concur – but the question is how to handle it now? Leave it and
> correct it later? Comment/remove it?

Write ? in the Version column alone instead of GCC? and in comment
say To be verified or something similar.

BTW, it would be really nice to use colors like
https://gcc.gnu.org/projects/cxx-status.html uses, use just GCC versions
instead of GCC version and No instead of N and use hyperlinks to
changes.html OpenMP ids (or just changes.html if we don't have an id).
And, for No we could in the future hyperlink to bugzilla if we file
PRs for those missing or WIP features which people can assign etc.

But that can be changed incrementally.

> Can you check whether you now like the bullet points? If so, I will
> update the .texi to match.

LGTM.

	Jakub


  reply	other threads:[~2022-05-17  9:00 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 [this message]
2022-05-17  9:50         ` Tobias Burnus
2022-05-17 10:02           ` Jakub Jelinek
2023-01-21 20:57           ` Gerald Pfeifer
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=YoNkLTpkpGRvtiUO@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).