[LLVMdev] [Openmp-dev] [cfe-dev] [RFC] OpenMP offload infrastructure (iteration 2)

Samuel F Antao sfantao at us.ibm.com
Wed Apr 29 12:28:25 PDT 2015


Alex,

Just to clarify my point, it may not be clear in my previous email. We
currently have a prototype implementation in https://github.com/clang-omp
that successfully uses the interface as described in the document. Of
course, we should be flexible in adapting the interface and compiler to
future changes in the OpenMP specification. But as the current spec, this
design has shown to work well for several platforms. So I believe, this is
a great starting point to get offloading working in clang and I am
committed to actively work on this with everyone to make that happen.

Thanks!
Samuel

2015-04-29 14:28 GMT-04:00 Alexandre Eichenberger <alexe at us.ibm.com>:

> Just a head up, but it looks like OpenMP 4.1 will go away of the map of the
> pointer as well as the pointee in maps...Since this is going away, we may
> want to revisit the interface with this respect. It has not been voted in
> yet, but we should know more in 2-3 weeks
>
> Alexandre
>
>
>
> From:   Samuel F Antao/Watson/IBM at IBMUS
> To:     Sergey Ostanevich <sergos.gnu at gmail.com>
> Cc:     openmp-dev at dcs-maillist2.engr.illinois.edu, Clang Developers
>             List <cfe-dev at cs.uiuc.edu>, "llvmdev at cs.uiuc.edu"
>             <llvmdev at cs.uiuc.edu>
> Date:   04/29/2015 02:19 PM
> Subject:        Re: [cfe-dev] [Openmp-dev] [RFC] OpenMP offload
> infrastructure
>             (iteration 2)
> Sent by:        cfe-dev-bounces at cs.uiuc.edu
>
>
>
> Hi Sergey,
>
> Thanks for putting the new version of the document together! I don't see
> any other issues. I strongly believe the approach described in the document
> is a nice way to get OpenMP offloading support in clang. I plan to start
> actively contributing code for this component of the OpenMP implementation
> soon.
>
>
> Thanks again,
> Samuel
>
> 2015-04-29 11:47 GMT-04:00 Sergey Ostanevich <sergos.gnu at gmail.com>:
>   Hi!
>
>   Here's an updated version - couple of misprints are fixed. Thank you
>   to Roel Jordans and Kelvin Li for pointing this out.
>   I put this on Google drive to avoid the mailing list restrictions,
>   feel free to complain on the accessibility issues.
>
>   http://goo.gl/L1rnKJ
>
>   Oh, and please - provide your positive feedback, if you don't see any
>   mistakes to be fixed. :)
>
>   Regards,
>   Sergey Ostanevich
>   Open Source Compilers
>   Intel Corporation
>
>   On Wed, Apr 8, 2015 at 7:19 PM, Sergey Ostanevich <sergos.gnu at gmail.com>
>   wrote:
>   > Hello everybody!
>   >
>   > To continue the original
>   > (http://article.gmane.org/gmane.comp.compilers.llvm.devel/75674)
>   > discussion of offload infrastructure I have an updated document with
>   > more details for your attention.
>   > The document is a consensus of the contributors representing a number
>   > of institutions: ANL, AMD,
>   > IBM, Intel and Texas Instruments.
>   >
>   > Our intent is to have a discussion and an approval from the community
>   > on the method we are going
>   > to implement, so when the time to submit patches will come there will
>   > be no surprises.
>   >
>   > Thank you,
>   > Sergey Ostanevich
>   > Open Source Compilers
>   > Intel Corporation
>   _______________________________________________
>   Openmp-dev mailing list
>   Openmp-dev at dcs-maillist2.engr.illinois.edu
>   http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
>
>
> _______________________________________________
> 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/llvm-dev/attachments/20150429/a4445857/attachment.html>


More information about the llvm-dev mailing list