[Openmp-dev] offloading library

Sergey Ostanevich sergos.gnu at gmail.com
Tue Jul 28 07:30:21 PDT 2015


Could you please comment my proposal of offload project organization at

Also having that big experience in different programming models, could you
please review the RTL (low level) interface described in
http://goo.gl/L1rnKJ - whether it is sufficient to implement support for
all model you aware of?


On Tue, Jun 9, 2015 at 3:30 PM, C Bergström <cbergstrom at pathscale.com>

> liboffload is not only useful for OMP alone. There's c++AMP, OpenCL
> (potentially) and other programming models which are doing
> "offloading". Gluing it to OMP reduces the visibility just as much the
> reason as why you haven't heard about other offloading runtimes. (They
> exist already)
> Not to mention the build infrastructure reasons. Look at the whole
> libunwind mess and how that eventually needed to get moved to an
> independent repo.
> I wish people (esp researchers) would look into the current state of
> things a bit more before just proposing the thing which seems obvious,
> but probably not the best long term plan.
> New repo, new project - has 3 layers: top layer API is exposed and
> meant for programming models to build on top of, middle is the
> transition to the bottom and exposes hardware hooks and bottom layer
> is hardware speicifc. I have this model today and it supports (PHI,
> AMD dGPU/APU and NVIDIA) across multiple programming models -
> including OMP4, OpenACC, C++AMP.. etc
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at dcs-maillist2.engr.illinois.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20150728/01d302ce/attachment.html>

More information about the Openmp-dev mailing list