search for: offload_maptypes

Displaying 3 results from an estimated 3 matches for "offload_maptypes".

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 enabled. For
2018 Apr 25
2
[LLVM][RFC] Representing the target device information in the LLVM IR
...%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 i64], [4 x i64]* @.offload_maptypes, i32 0, i32 0)) Thanks, Jin From: Friedman, Eli [mailto:efriedma at codeaurora.org] Sent: Wednesday, April 25, 2018 3:18 PM To: Lin, Jin <jin.lin at intel.com>; 'llvm-dev at lists.llvm.org' <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] [LLVM][RFC] Representing the targ...
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