[Openmp-dev] Location for omptarget

[Paul Osmialowski via Openmp-dev]

On 30/09/2016 12:42, Hahnfeld, Jonas via Openmp-dev wrote:
>> -----Original Message-----
>> From: C Bergström [mailto:cbergstrom at pathscale.com]
>> Sent: Friday, September 30, 2016 1:35 PM
>> To: Hahnfeld, Jonas
>> Cc: Narayanaswamy, Ravi; LLVM-OpenMP (openmp-dev at lists.llvm.org)
>> Subject: Re: [Openmp-dev] Location for omptarget
>>
>> On Fri, Sep 30, 2016 at 2:23 PM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-
>> aachen.de> wrote:
>>>
>>> We already have "liboffload", I don't think that’s a clever name... I'm fine
>> with "libomptarget" but I don't really care too much about the name.
>>
>> Some semi-sarcastic questions if you don't mind
>> ------------
>> So are target regions offloaded? What does liboffload do if it doesn't help a
>> target region get offloaded onto the device? (I realize that you can
>> implement a target region as tasks, but why can't we leverage the existing
>> task code to accomplish that then..
>
> I think that's a misunderstanding: I'm only saying that there already is Intel's liboffload that does exactly this but that will not be compatible with Clang. See http://llvm.org/svn/llvm-project/openmp/trunk/offload/
>

Is libomptarget compatible with clang or is it compatible with 
clang-omp? Last time I checked it, my findings were that clang wasn't 
ready for it and I had to use clang-omp instead. Note that I've found 
libomptarget quite interesting and easily extensible and I hope it will 
soon get it's way to LLVM projects family (no matter if it's in or out 
of OpenMP runtime library, along with or as a replacement to liboffload).