public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikel Mendizabal <mikel.mendizabal.morentin@desy.de>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC and OpenACC
Date: Wed, 12 Jan 2022 11:01:10 +0100	[thread overview]
Message-ID: <B7825FDA-1AD4-446F-9AE5-4F8AD4E6CB47@desy.de> (raw)
In-Reply-To: <CAFiYyc0DprMz2=BmbbKZYNH9j3CXkNVRj-1JOVE=X9M+Oyr3DQ@mail.gmail.com>

Dear Richard,

Thanks a lot for the fast response. Here I send you a self contained example. I took it from openACC tutorial in [1]. I modified the code and added a dummy vector of size 1, lines 140-160 in the attached file (jsolvef_mikel.F90). The dummy vector (residual_v)  is the array form of the variable residual.

If the reduction clause (line 142) is commented both residual and residual_v give the same result. If in the reduction clause residual_v is given a compilation error appears, that the reduction clause does not support this variable datatype. In [2] I added the OpenACC 3.1 documentation. In section 1.12 the changes from v2.6 to v2.7 are described. More precisely, in line 612-613 the next is quoted:

"Arrays, subarrays and composite variables are now allowed in reduction clauses; see Sections 2.9.11 reduction clause and 2.5.14 reduction clause.”
I hope I could explain myself properly!
Thanks a lot :) 

Mikel Mendizabal


[1] https://github.com/OpenACCUserGroup/openacc-users-group/blob/master/Contributed_Sample_Codes/Tutorial1/solver/jsolvef.F90 <https://github.com/OpenACCUserGroup/openacc-users-group/blob/master/Contributed_Sample_Codes/Tutorial1/solver/jsolvef.F90> 
[2] https://www.openacc.org/sites/default/files/inline-images/Specification/OpenACC-3.1-final.pdf <https://www.openacc.org/sites/default/files/inline-images/Specification/OpenACC-3.1-final.pdf> 



> On 11. Jan 2022, at 14:26, Richard Biener <richard.guenther@gmail.com> wrote:
> 
> On Tue, Jan 11, 2022 at 1:52 PM Mikel Mendizabal via Gcc
> <gcc@gcc.gnu.org <mailto:gcc@gcc.gnu.org>> wrote:
>> 
>> Dear GCC developers,
>> 
>> In the past year we started the offload of our software to GPUs. We decided to go with OpenACC. The program we are trying to offload is Millepede2 (MP2),  a tracker alignment software used to align the CMS experiment tracker at the large hadron collider.
>> 
>> We are using gcc as our main compiler. However, we found a major inconvenience with OpenACC 2.6, the REDUCTION clause does not accept arrays. Thus, it not possible for us to parallelise our largest loops due to array dependencies. We managed to offload MP2 for small datasets, we worked around the reduction issue. Nonetheless, if our alignment campaign is large the workarounds are not useful anymore.
>> 
>> I went thought the new versions of OpenACC and I found that v2.7 accepts arrays for the REDUCTION clause. I was wondering if it is in your plans to include a newer version of OpenACC for the next releases.
> 
> Can you produce a self-contained example with an array for the
> REDUCTION clause that should be accepted with OpenACC v2.7?
> 
> Thanks,
> Richard.
> 
>> Sincerely,
>> Mikel Mendizabal


  reply	other threads:[~2022-01-12 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 12:50 Mikel Mendizabal
2022-01-11 13:26 ` Richard Biener
2022-01-12 10:01   ` Mikel Mendizabal [this message]
2022-01-12 11:53     ` Tobias Burnus

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=B7825FDA-1AD4-446F-9AE5-4F8AD4E6CB47@desy.de \
    --to=mikel.mendizabal.morentin@desy.de \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).