search for: offload_baseptrs

Displaying 8 results from an estimated 8 matches for "offload_baseptrs".

2018 Apr 25
0
[LLVM][RFC] Representing the target device information in the LLVM IR
...ssumes the > variable @gg is passed by reference. > > Here is the corresponding IR on the host side. > >   %0 = load double, double* @gg, align 8, !tbaa !3 > >   %1 = bitcast double %0 to i64 > >    … > >   %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* > %.offload_baseptrs, i32 0, i32 2 > >   %13 = bitcast i8** %12 to i64* > >   store i64 %1, i64* %13, align 8 > Could you describe the overall process of calling an offloaded function in a bit more detail?  How do you describe the ABI of the called function to the OpenMP runtime? I suspect you should...
2018 Apr 25
2
[LLVM][RFC] Representing the target device information in the LLVM IR
...t i386-pc-linux-gnu cannot get the correct value since it assumes the variable @gg is passed by reference. Here is the corresponding IR on the host side. %0 = load double, double* @gg, align 8, !tbaa !3 %1 = bitcast double %0 to i64 ... %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* %.offload_baseptrs, i32 0, i32 2 %13 = bitcast i8** %12 to i64* store i64 %1, i64* %13, align 8 ... %20 = call i32 @__tgt_target(i64 -1, i8* @.omp_offload.region_id, i32 4, i8** %4, i8** %6, i64* getelementptr inbounds ([4 x i64], [4 x i64]* @.offload_sizes, i32 0, i32 0), i64* getelementptr inbounds ([4 x i6...
2018 Apr 26
4
[LLVM][RFC] Representing the target device information in the LLVM IR
...t i386-pc-linux-gnu cannot get the correct value since it assumes the variable @gg is passed by reference. Here is the corresponding IR on the host side. %0 = load double, double* @gg, align 8, !tbaa !3 %1 = bitcast double %0 to i64 ... %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* %.offload_baseptrs, i32 0, i32 2 %13 = bitcast i8** %12 to i64* store i64 %1, i64* %13, align 8 Could you describe the overall process of calling an offloaded function in a bit more detail? How do you describe the ABI of the called function to the OpenMP runtime? I suspect you shouldn't be trying to store...
2018 Apr 26
0
[LLVM][RFC] Representing the target device information in the LLVM IR
...y reference.   > >   > > Here is the corresponding IR on the host side. > >   %0 = load double, double* @gg, align 8, !tbaa !3 > >   %1 = bitcast double %0 to i64 > >    … > >   %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* > %.offload_baseptrs, i32 0, i32 2 > >   %13 = bitcast i8** %12 to i64* > >   store i64 %1, i64* %13, align 8 > > > Could you describe the overall process of calling an offloaded > function in a bit more detail?  How do you describe the ABI of the > called function to the OpenMP runti...
2018 Apr 27
2
[LLVM][RFC] Representing the target device information in the LLVM IR
...  > > Here is the corresponding IR on the host side. > >   %0 = load double, double* @gg, align 8, !tbaa !3 > >   %1 = bitcast double %0 to i64 > >    … > >   %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* > %.offload_baseptrs, i32 0, i32 2 > >   %13 = bitcast i8** %12 to i64* > >   store i64 %1, i64* %13, align 8 > > > Could you describe the overall process of calling an offloaded > function in a bit more detail?  How do you describe the ABI of the > called function...
2018 Apr 27
0
[LLVM][RFC] Representing the target device information in the LLVM IR
...t i386-pc-linux-gnu cannot get the correct value since it assumes the variable @gg is passed by reference. Here is the corresponding IR on the host side. %0 = load double, double* @gg, align 8, !tbaa !3 %1 = bitcast double %0 to i64 ... %12 = getelementptr inbounds [4 x i8*], [4 x i8*]* %.offload_baseptrs, i32 0, i32 2 %13 = bitcast i8** %12 to i64* store i64 %1, i64* %13, align 8 Could you describe the overall process of calling an offloaded function in a bit more detail? How do you describe the ABI of the called function to the OpenMP runtime? I suspect you shouldn't be trying to store...
2018 Apr 25
0
[LLVM][RFC] Representing the target device information in the LLVM IR
On 4/25/2018 3:05 PM, Lin, Jin via llvm-dev wrote: > > RFC: Representing the target device information in the LLVM IR > > =========================================================================== > > Why this RFC change? > > ================= > > The target device information needs to be passed to the LLVM backend > when OpenMP backend outlining is
2018 Apr 25
2
[LLVM][RFC] Representing the target device information in the LLVM IR
RFC: Representing the target device information in the LLVM IR =========================================================================== Why this RFC change? ================= The target device information needs to be passed to the LLVM backend when OpenMP backend outlining is enabled. For example, for multiple target devices, the target compilation has to generate a single host to support all