From: Jakub Jelinek <jakub@redhat.com>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: [openacc] fortran loop clauses and splitting
Date: Tue, 01 Dec 2015 08:33:00 -0000 [thread overview]
Message-ID: <20151201083342.GP5675@tucnak.redhat.com> (raw)
In-Reply-To: <565C8EA6.1040604@codesourcery.com>
On Mon, Nov 30, 2015 at 10:00:06AM -0800, Cesar Philippidis wrote:
> This patch contains the following bug fixes:
>
> * Teaches gfortran to accept both num and static gang arguments inside
> same clause. E.g. gang(num:10, static:30). Currently, gfortran only
> allows one of those arguments to appear in a gang clause.
>
> * Make the diagnostics reported by resovle_oacc_positive_int_expr more
> accurate for worker and vector clauses.
>
> * Updates how combined loops are split to account for the renamed gang
> clause members in gfc_omp_clauses. Also corrected a bug that Tom
> discovered in the c front end where combined reductions were being
> attached to kernels and parallel constructs. Now, they are only
> associated with the split acc loop.
>
> Is this OK for trunk?
Ok, thanks.
Jakub
prev parent reply other threads:[~2015-12-01 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 18:00 Cesar Philippidis
2015-12-01 8:33 ` 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=20151201083342.GP5675@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=cesar@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@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).