Displaying 3 results from an estimated 3 matches for "first_private".
2018 Apr 27
2
[LLVM][RFC] Representing the target device information in the LLVM IR
...the object mapped are of
> different sizes between host and target with different ABI.
>
Why are you not trying to address that issue?
-Hal
> The issue is when the objects are of same size like double which is
> 8bytes on both 32bit and 64bit platform. If a double is used in a
> first_private on a target clause, the 64 bit side will pass it as
> value whereas on the 32bit side since the value does not fit in the
> argument it will be passed as pointer to a double. There will be a
> mis-match at the call site and entry site on this value.
>
> The main reason for this ch...
2018 Apr 27
0
[LLVM][RFC] Representing the target device information in the LLVM IR
Hi Hal,
We are not trying to address issues where the object mapped are of different sizes between host and target with different ABI. The issue is when the objects are of same size like double which is 8bytes on both 32bit and 64bit platform. If a double is used in a first_private on a target clause, the 64 bit side will pass it as value whereas on the 32bit side since the value does not fit in the argument it will be passed as pointer to a double. There will be a mis-match at the call site and entry site on this value.
The main reason for this change is that when we do b...
2018 Apr 26
4
[LLVM][RFC] Representing the target device information in the LLVM IR
For the firstprivate clause, the compiler generates code to pass it by value or by reference to the outlined function. The reason the first private scalars is generally passed by value is for the performance reason.
For this particular case, the compiler cannot generate code to pass the double @gg by value under i386-pc-linux-gnu since the value is 64 bit while the architecture is 32bit.
For the