public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
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>,
	"Vollweiler, Marcel" <marcel@codesourcery.com>
Subject: Re: [Patch] Fortran/OpenMP: Fix depend-clause handling for c_ptr (was: [Patch] Fortran/OpenMP: Fix depend-clause handling)
Date: Tue, 15 Feb 2022 18:36:36 +0100	[thread overview]
Message-ID: <20220215173636.GS2646553@tucnak> (raw)
In-Reply-To: <17f5dcd9-c658-dec5-0b5d-debc0efb6cf7@codesourcery.com>

On Tue, Feb 15, 2022 at 06:01:09PM +0100, Tobias Burnus wrote:
> OK?

Ok.

> Fortran/OpenMP: Fix depend-clause handling for c_ptr
> 
> gcc/fortran/ChangeLog:
> 
> 	* trans-openmp.cc (gfc_trans_omp_depobj): Fix to alloc/ptr dummy
> 	and for c_ptr.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gfortran.dg/gomp/depend-4.f90: Add VALUE test, update scan test.
> 	* gfortran.dg/gomp/depend-5.f90: Fix scan tree for -m32.
> 	* gfortran.dg/gomp/depend-6.f90: New test.
> 
>  gcc/fortran/trans-openmp.cc                 |   7 +-
>  gcc/testsuite/gfortran.dg/gomp/depend-4.f90 |  29 +++-
>  gcc/testsuite/gfortran.dg/gomp/depend-5.f90 |  12 +-
>  gcc/testsuite/gfortran.dg/gomp/depend-6.f90 | 259 ++++++++++++++++++++++++++++
>  4 files changed, 295 insertions(+), 12 deletions(-)

	Jakub


  reply	other threads:[~2022-02-15 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 10:26 [Patch] Fortran/OpenMP: Fix depend-clause handling Tobias Burnus
2022-02-15 10:56 ` Jakub Jelinek
2022-02-15 17:01   ` [Patch] Fortran/OpenMP: Fix depend-clause handling for c_ptr (was: [Patch] Fortran/OpenMP: Fix depend-clause handling) Tobias Burnus
2022-02-15 17:36     ` Jakub Jelinek [this message]
2022-02-15 16:38 ` [Patch] Fortran/OpenMP: Fix depend-clause handling 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=20220215173636.GS2646553@tucnak \
    --to=jakub@redhat.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=marcel@codesourcery.com \
    --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).