[Openmp-dev] Removing liboffload from repository

Churbanov, Andrey via Openmp-dev openmp-dev at lists.llvm.org
Tue Jun 19 10:29:52 PDT 2018


Sure, I am OK with this cleanup.

Thanks,
Andrey

-----Original Message-----
From: Jonas Hahnfeld [mailto:hahnjo at hahnjo.de] 
Sent: Tuesday, June 19, 2018 8:20 PM
To: Peyton, Jonathan L <jonathan.l.peyton at intel.com>; Churbanov, Andrey <Andrey.Churbanov at intel.com>
Cc: Hal Finkel <hfinkel at anl.gov>; Narayanaswamy, Ravi <ravi.narayanaswamy at intel.com>; openmp-dev (openmp-dev at lists.llvm.org) <openmp-dev at lists.llvm.org>
Subject: Re: [Openmp-dev] Removing liboffload from repository

Andrey, are you ok as the code owner?

Jonas

On 2018-06-14 19:14, Peyton, Jonathan L wrote:
> I think you can go ahead and remove it.
> 
> -- Johnny
> 
> -----Original Message-----
> From: Openmp-dev [mailto:openmp-dev-bounces at lists.llvm.org] On Behalf 
> Of Hal Finkel via Openmp-dev
> Sent: Thursday, June 14, 2018 9:25 AM
> To: Narayanaswamy, Ravi <ravi.narayanaswamy at intel.com>; Jonas Hahnfeld 
> <hahnjo at hahnjo.de>; openmp-dev (openmp-dev at lists.llvm.org) 
> <openmp-dev at lists.llvm.org>
> Subject: Re: [Openmp-dev] Removing liboffload from repository
> 
> 
> On 06/12/2018 11:34 AM, Narayanaswamy, Ravi via Openmp-dev wrote:
>> I agree.
> 
> +1
> 
>  -Hal
> 
>> In our last LLVM Multi-company offload meeting I asked if it can be 
>> removed and nobody had any objection.
>> Thanks
>> Ravi
>> 
>> -----Original Message-----
>> From: Openmp-dev [mailto:openmp-dev-bounces at lists.llvm.org] On Behalf 
>> Of Jonas Hahnfeld via Openmp-dev
>> Sent: Tuesday, June 12, 2018 9:30 AM
>> To: openmp-dev at lists.llvm.org
>> Subject: [Openmp-dev] Removing liboffload from repository
>> 
>> Hi all,
>> 
>> I'd like to propose removing liboffload (the 'offload/' directory) 
>> from the openmp repository.
>> 1) This is an old dump from openmprtl.org which was never updated 
>> (The current version doesn't even build / work with newer software 
>> stacks!), even though Intel continued doing newer releases.
>> 2) The library was never integrated into LLVM's build system, you 
>> have to manually call 'make' with the right parameters.
>> 3) The library is meant for Intel's Xeon Phi Knights Corner 
>> coprocessor.
>> AFAIK there only were variants of Knights Landing that serve as host 
>> processor (coprocessor cards were announced but never released). As 
>> of last year, even its successor Knights Hill has been declared dead 
>> and the whole line is now discontinued.
>> 
>> With libomptarget getting more mature it's quite confusing for our 
>> users that there are two libraries apparently doing offloading.
>> 
>> Thoughts?
>> Jonas
>> _______________________________________________
>> Openmp-dev mailing list
>> Openmp-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
>> _______________________________________________
>> Openmp-dev mailing list
>> Openmp-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> 
> --
> Hal Finkel
> Lead, Compiler Technology and Programming Languages Leadership 
> Computing Facility Argonne National Laboratory
> 
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev

--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


More information about the Openmp-dev mailing list