[llvm-dev] [Openmp-dev] [RFC] Proposed interplay of Clang & Flang & LLVM wrt. OpenMP [@Flang-dev]

Alexey Bataev via llvm-dev llvm-dev at lists.llvm.org
Thu May 2 08:54:14 PDT 2019

What you're talking about is the late outlining, which should be the
part of the LLVM. As I understand, Intel already has preliminary
implementation of this and they promised to publish it in May.

Also, this was discussed some time ago, if I remember it correctly, and
it was recommended to implement this common codegen as a kind of plugin.
I don't remember the final result of this discussion, though.

Best regards,
Alexey Bataev

02.05.2019 11:33, Doerfert, Johannes via Openmp-dev пишет:
> Hi,
> [I started this discussion on a single mailing list (flang-dev [0]) but
>  this is a notice to the others (llvm, clang, openmp) so we hopefully
>  get all interested parties involved.]
> This is an RFC for the design of the OpenMP front-ends under the LLVM
> umbrella. It is necessary to talk about this now as Flang (aka. F18) is
> maturing at a very promising rate and about to become a sub-project next
> to Clang.
> Keep AST nodes and Sema separated but unify LLVM-IR generation for
> OpenMP constructs based on the (almost) identical OpenMP directive
> level.
> For more information and to participate in the discussion, please see
> the flang-dev post [0].
> Thanks,
>   Johannes
> [0] http://lists.flang-compiler.org/pipermail/flang-dev_lists.flang-compiler.org/2019-May/000197.html
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190502/c063f680/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190502/c063f680/attachment.sig>

More information about the llvm-dev mailing list