[llvm-dev] Code owner for openmp offloading

Kiran Chandramohan via llvm-dev llvm-dev at lists.llvm.org
Wed May 19 07:16:21 PDT 2021


Hello all,

I would like to extend my support for this nomination.

For the past two years, Johannes has been providing leadership and consultation for enabling OpenMP and OpenACC support in Flang. This has led to the creation of the OpenMP IRBuilder for code-sharing between the Clang, Flang and MLIR projects for OpenMP and OpenACC. Johannes is our primary contact from the core OpenMP team.

We recently started work on supporting the target constructs in OpenMP (and OpenACC) in Flang and MLIR. Plan is to reuse the code and infrastructure that is there in clang/llvm. Johannes being the code owner will be an acknowledgement of his great contributions as well as will enable faster decision making and progress in this area.

Thanks,
Kiran

________________________________
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Jon Chesterfield via llvm-dev <llvm-dev at lists.llvm.org>
Sent: 14 May 2021 18:33
To: llvm-dev <llvm-dev at lists.llvm.org>
Cc: andrey.churbanov at intel.com <andrey.churbanov at intel.com>; Doerfert, Johannes <jdoerfert at anl.gov>
Subject: [llvm-dev] Code owner for openmp offloading

Hello LLVM,

Openmp target offloading (GPUs, at present) has turned into a substantial project in it's own right with mostly orthogonal concerns to openmp host. There's been a multiyear effort to get nvidia and amdgpu targets running, with host + device + clang + llvm code implemented, weekly calls and annual gsoc students.

I would like to propose a code owner for openmp target offloading. Specifically I would like to nominate Johannes, as in my opinion he's been doing that role for the last couple of years anyway, and is a reliable choice for first point of contact for new contributors.

Objections? Support? Other?

Thanks all,

Jon







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210519/ee9b9876/attachment.html>


More information about the llvm-dev mailing list