From: Jakub Jelinek <jakub@redhat.com>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Fortran List <fortran@gcc.gnu.org>,
Thomas Schwinge <thomas_schwinge@mentor.com>
Subject: Re: OpenACC wait clause
Date: Tue, 28 Jun 2016 07:08:00 -0000 [thread overview]
Message-ID: <20160628070822.GV7387@tucnak.redhat.com> (raw)
In-Reply-To: <5771B519.90106@codesourcery.com>
On Mon, Jun 27, 2016 at 04:22:01PM -0700, Cesar Philippidis wrote:
> + while (ret == MATCH_YES)
> {
> - if (cp->gang_static)
> - return MATCH_ERROR;
> + if (gfc_match (" static :") == MATCH_YES)
> + {
> + if (cp->gang_static)
> + return MATCH_ERROR;
It might be useful to gfc_error before this (i.e. follow a rule,
if you return MATCH_ERROR where MATCH_ERROR has not been returned before,
you emit gfc_error, if it has been returned from nested calls, you don't),
but it is not a big deal, worse case you get the cryptic generic error.
Let's keep it as is for now.
> + /* The 'num' arugment is optional. */
Typo, argument.
> + if (gfc_match (" num :") == MATCH_ERROR)
> + return MATCH_ERROR;
This is unnecessary (I mean the == MATCH_ERROR check), gfc_match for
no % operands in it will never return MATCH_ERROR (why would it?),
just MATCH_YES or MATCH_NO.
> + else if (gwv == GOMP_DIM_VECTOR)
> + {
> + /* The 'length' arugment is optional. */
See above.
> + if (gfc_match (" length :") == MATCH_ERROR)
And once more.
> @@ -1275,8 +1308,8 @@ gfc_match_omp_clauses (gfc_omp_clauses **cp, uint64_t mask,
> continue;
> if ((mask & OMP_CLAUSE_TILE)
> && !c->tile_list
> - && match_oacc_expr_list ("tile (", &c->tile_list,
> - true) == MATCH_YES)
> + && match_oacc_expr_list ("tile (", &c->tile_list, true)
> + == MATCH_YES)
Why this hunk? I think it is better to put the line break before the last
argument here, you don't have to decide if it shouldn't be surrounded by
&& (match_oacc... (...)
== MATCH_YES))
Otherwise LGTM.
Jakub
prev parent reply other threads:[~2016-06-28 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160607111307.GQ7387@tucnak.redhat.com>
[not found] ` <5756E1B6.605@codesourcery.com>
[not found] ` <20160607150252.GS7387@tucnak.redhat.com>
2016-06-17 3:22 ` Cesar Philippidis
2016-06-17 14:34 ` Jakub Jelinek
2016-06-24 15:42 ` Cesar Philippidis
2016-06-24 15:53 ` Jakub Jelinek
2016-06-27 18:36 ` Cesar Philippidis
2016-06-27 19:23 ` Jakub Jelinek
2016-06-27 23:22 ` Cesar Philippidis
2016-06-28 7:08 ` 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=20160628070822.GV7387@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=cesar@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas_schwinge@mentor.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).