We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No response
Device-only allocation for the pool allocator/stack.
Currently the stack is created and allocated on device like that:
REAL(KIND=JPRB), ALLOCATABLE :: ZSTACK(:, :) ISTSZ = ... ALLOCATE (ZSTACK(ISTSZ, NGPBLKS)) !$acc data create( ZSTACK ) ... !$acc end data DEALLOCATE (ZSTACK)
thus the stack is both allocated on host and device, although we only require it to be on the device.
To only allocate it on device we could:
declare device_resident
REAL(KIND=JPRB), ALLOCATABLE :: ZSTACK(:, :) ISTSZ = ... !$acc declare device_resident(ZSTACK) allocate(ZSTACK(ISTZ, NGPBLKS)) ... deallocate(ZSTACK)
however, it is not clear whether NVIDIA adheres to the standard: StackOverflow: (NVHPC aka PGI) treats device_resident as a create?!
REAL(KIND=JPRB), ALLOCATABLE, DEVICE :: ZSTACK(:, :)
acc_malloc()
c_ptr
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
Device-only allocation for the pool allocator/stack.
Describe alternatives you've considered
No response
Additional context
Currently the stack is created and allocated on device like that:
thus the stack is both allocated on host and device, although we only require it to be on the device.
To only allocate it on device we could:
declare device_resident
however, it is not clear whether NVIDIA adheres to the standard: StackOverflow: (NVHPC aka PGI) treats device_resident as a create?!
REAL(KIND=JPRB), ALLOCATABLE, DEVICE :: ZSTACK(:, :)
acc_malloc()
c_ptr
....Organisation
No response
The text was updated successfully, but these errors were encountered: