- User Since
- Nov 11 2015, 7:57 AM (384 w, 4 d)
Mon, Mar 20
Sep 30 2022
This message could be printed when LIBOMPTARGET_INFO="something". I don't think it should be printed by default as it could be false positive.
Sep 29 2022
I am not sure if we should generate this message. The spec says "Each list item must have a corresponding list item in the device data environment or be accessible on the target device."
The pointer may be in the unified_shared_memory.
Sep 26 2022
Sep 21 2022
Apr 22 2022
Apr 7 2022
Mar 29 2022
Feb 11 2022
Thanks Andrey for the fix
Jan 24 2022
Nov 10 2021
Oct 5 2021
Sep 22 2021
Sep 10 2021
Sep 9 2021
Aug 6 2021
Aug 3 2021
Jul 23 2021
You should not be using kmpc in libomptarget
Jul 9 2021
If the current behavior is only the pointer field of the struct and not other members of the struct are updated after the array is allocated and copied.
Are you concerned about a misbehavior here?
I am just answering the question George asked about the expected behavior.
#pragma omp target map(s1.p[0:10])
Mar 18 2021
How much time do you think you need to resolve or conclude to revert or disable with macros in 12.0
Some would like to stabilize their performance numbers and would like to do it as early as possible.
Prefer if you remove this from the mail " [AMD Official Use Only - Internal Distribution Only]"
Mar 15 2021
Reasonable to drop the device number for alloc_host as all devices should be able to access host memory.
Mar 1 2021
This is where we are heading towards in OpenMP spec
The mandatory value specifies that program execution is terminated if a device construct or
device memory routine is encountered and the device is not available or is not supported by the
implementation. or if omp_get_num_devices() would return 0.
If OMP_TARGET_OFFLOAD=mandatory it will not fail but just return
Feb 18 2021
Jan 27 2021
Dec 1 2020
Sep 25 2020
Sep 23 2020
Can you also remove the definition in the header file include/omptarget.h
Sep 9 2020
Jul 24 2020
Jul 23 2020
Jun 19 2020
How do you plan to support
#pragma omp target update to (arr[1:2][1:2][0:2], x, b[1:5][0:2])
Are you going to split this into 3 updates since your are using the arg fields.
Jan 29 2020
I don't recall saying needs changes.
Aug 14 2019
Jun 14 2019
Nov 29 2018
Can you enable LIBOMPTARGET_DEBUG and see if this is printed from libomptarget to confirm libomptarget is loaded and its api is used
DP("Call to omp_get_num_devices returning %zd\n", Devices_size);
Aug 30 2018
I did not see the code where check is done if Nestingdepth is 0 at end of compilation.
Aug 29 2018
We should just go with generating an error if the DeclareTargetNestingLevel is not 0 at the end of compilation unit.
Hard to detect if user accidentally forgot to have end declare in header file and had it in the include file or it was intentional.
Aug 28 2018
Is there a way to tell if the header files have matching omp declare target/omp end declare target.
The reason is if one of the header files is missing a matching omp end declare target all files which include it will end up having everything marked with declare target
Aug 24 2018
Aug 23 2018
If the objects which are copied are not compatible between host and target due to use of pointers which have different size in a structure then it is users responsibility.
I am more interested in where you allocate memory on device you get back an opaque object of size 64. The opaque object may be 64bit device pointer or a high 32bit pointer to device memory and low 32bit offset from that memory or it can be a pointer to a structure which has other information. The idea having libomptarget is to provide a thin layer between compiler and device specific plugin and we need to support different types of plugin.
Provide additional APIs in plugins if necessary to accomplish the arithmetic operations.
By doing arithmetic for target address in libomptarget you are assuming the pointer size is 64.
Aug 10 2018
Alex: If you feel strongly about your request, I will be happy to move the code into CheckDeviceAndCtors.
It is just a suggestion. Either way is fine.
Aug 9 2018
Aug 2 2018
It may be named libOMPtarget and is in openmp projects but we want to use the offloading library with other runtime libraries.
We should not be having calls to _-kmpc_omp_taskwait in libomptarget.
The wait should be done in the user code and then libomptarget routine should be called.
Mar 16 2018
DEFAULT implies MANDATORY or DISABLED. Don't need to communicate to libomp
Mar 15 2018
Openmp has defined OMP_TARGET_OFFLOAD to control offloading, We should be using this
Mar 7 2018
Jan 6 2016
OpenMP says : " If the corresponding list item is not present in the device data environment then no assignment occurs to or from the original list item."