public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cesar Philippidis <cesar@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Fortran List	<fortran@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>
Subject: [openacc] clean up acc directive matching in fortran
Date: Fri, 17 Jun 2016 03:31:00 -0000	[thread overview]
Message-ID: <57636EEC.10609@codesourcery.com> (raw)

This patch introduces a match_acc function to the fortran FE. It's
almost identical to match_omp, but it passes openacc = true to
gfc_match_omp_clauses. I supposed I could have consolidated those two
functions, but they are reasonably simple so I left them separate. Maybe
a follow up patch can consolidate them. I was able to eliminate a lot of
duplicate code with this function.

Is this ok for trunk and gcc-6?

Cesar

             reply	other threads:[~2016-06-17  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  3:31 Cesar Philippidis [this message]
2016-06-17  3:31 ` Cesar Philippidis
2016-06-17  8:40   ` Tobias Burnus
2016-06-17 14:07     ` Jakub Jelinek

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=57636EEC.10609@codesourcery.com \
    --to=cesar@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).