PGI User Forum

[AROM]

Hi Mat,

This topic is continuation of this one. The problem was how PGI works with private arrays. So I had to convert private arrays to global arrays with an appropriate size. It dramatically increased memory requirements on CPU cite. So I'd like to extend those topic and ask:
What is the correct way to work with "private" arrays?

In my kernel I have hundred of private arrays. RHO, CPM, XXLV, XXLS is not full list. Those arrays are allocated on GPU with "acc data create" directive. Thus it takes much time for memory allocation and freeing. So I'd like to allocate big chunk of memory and split it among "private" arrays.

[mkcolg]

Hi Alexey,

I tried to recreate the error you logged in as #263, but was unable. Granted, I may not have been reproducing it correctly since I needed to put your file into the full application in order to get the dependent modules. Have you made changes to the dependent mod files? If so, can you wrap up a package with all the files? Any flag extra flags added to the default list other than -acc?

As for the second issue, at this point we don't yet support F90 pointers in data clauses. It sounds like that we're almost there, one small issue left, but they want to get in a lot more testing before adding it.

Are you able to use the "private" clause or was this the problem with your earlier post?

[AROM]

Hi Mat!

I've updated #263.

Refer to private variables... I have some problems with private variables in another example (see #261).

In this case (RHO, CMP....) I tried to solve the problem of allocating hundreds arrays. It takes ~50% of kernel execution time.