public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH][OpenACC] update gfortran's tile clause error handling
Date: Tue, 04 Dec 2018 14:47:00 -0000	[thread overview]
Message-ID: <20181204140703.GW12380@tucnak> (raw)
In-Reply-To: <e1b2337a-ef32-76f3-bc94-658155b08b62@codesourcery.com>

On Tue, Aug 07, 2018 at 02:47:07PM -0700, Cesar Philippidis wrote:
> This patch updates how the OpenACC tile clause is handled in the Fortran
> FE to match it's behavior in C/C++. Specifically, the tile clause now
> errors on negative integer arguments, instead of emitting a warning.
> 
> Is this OK for trunk?

I've reviewed this already in some other patch, this is not ok, if
that is what you want for OpenACC, you need to copy the function to some
other one and adjust callers to use it for OpenACC clauses only.

> >From af39a6d65cfb46397fa62c88521189002fb3d705 Mon Sep 17 00:00:00 2001
> From: Cesar Philippidis <cesar@codesourcery.com>
> Date: Mon, 3 Oct 2016 13:58:59 +0000
> Subject: [PATCH] [OpenACC] update gfortran's tile clause error handling
> 
> 2018-XX-YY  Cesar Philippidis  <cesar@codesourcery.com>
> 
> 	gcc/fortran/
> 	* openmp.c (resolve_positive_int_expr): Promote the warning to an
> 	error.
> 
> 	gcc/testsuite/
> 	* gfortran.dg/goacc/loop-2.f95: Change expected tile clause
> 	warnings to errors.
> 	* gfortran.dg/goacc/loop-5.f95: Likewise.
> 	* gfortran.dg/goacc/sie.f95: Likewise.
> 	* gfortran.dg/goacc/tile-1.f90: New test.
> 	* gfortran.dg/goacc/tile-2.f90: New test.

	Jakub

  reply	other threads:[~2018-12-04 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 14:07 [gomp4] " Cesar Philippidis
2016-10-03 14:35 ` Nathan Sidwell
     [not found] ` <87a13495-a378-b5e1-8223-0f5679f98356@mentor.com>
     [not found]   ` <20161111103441.GY3541@tucnak.redhat.com>
     [not found]     ` <cbe5aca8-77c5-0057-1381-4a99e43b4318@codesourcery.com>
     [not found]       ` <20161118112451.GW3541@tucnak.redhat.com>
     [not found]         ` <7467e478-cee5-b694-2988-e6887f25fa17@codesourcery.com>
2018-08-07 21:47           ` [PATCH][OpenACC] " Cesar Philippidis
2018-12-04 14:47             ` Jakub Jelinek [this message]
     [not found]             ` <87d0lvgorx.fsf@euler.schwinge.homeip.net>
     [not found]               ` <87k1e9iapl.fsf@euler.schwinge.homeip.net>
     [not found]                 ` <20190529145245.GU19695@tucnak>
2019-06-06  8:06                   ` Negative arguments in OpenMP 'num_threads' clause etc Thomas Schwinge

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=20181204140703.GW12380@tucnak \
    --to=jakub@redhat.com \
    --cc=cesar@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    /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).