From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran: Cleanup OpenMP match{o,s,do,ds} macros
Date: Thu, 30 Jun 2022 14:51:38 +0200 [thread overview]
Message-ID: <Yr2cWqrHR1+lJB8W@tucnak> (raw)
In-Reply-To: <783d48b1-3939-19c6-78ce-dc0e0cc59231@codesourcery.com>
On Thu, Jun 30, 2022 at 02:30:24PM +0200, Tobias Burnus wrote:
> OK for mainline - or should I put that patch into the bin?
Not sure, the other match* macros also aren't wrappers
around another macro and with the internal macro it means we'll
need to parse more many times (even when we then fold the conditions quite
early).
> +/* Like match, but with some special handling:
> + - dosimd - if false, don't do anything if not -fopenmp,
> + otherwise do match_word_omp_simd matching
> + - if dospec_only: if spec_only, goto do_spec_only after matching.
> +
> + If the directive matched but the clauses failed, do not start
> + matching the next directive in the same switch statement. */
> +
> +#define match_internal(match_simd, match_spec_only, keyword, subr, st) \
It at least should be matcho_internal or have the OpenMP stuff in the name
somehow, because it is quite OpenMP specific and isn't used by match or
matcha etc.
> +/* Like match. Does simd matching; sets flag simd_matched if keyword matched. */
Twice missing 2 spaces after .
Jakub
prev parent reply other threads:[~2022-06-30 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:30 Tobias Burnus
2022-06-30 12:51 ` Jakub Jelinek [this message]
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=Yr2cWqrHR1+lJB8W@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).