[cfe-dev] [llvm-dev] MLIR for clang

[Chris Lattner via cfe-dev]

Hi Michael (and others), here are the slides from the CGO presentation, <https://docs.google.com/presentation/d/11-VjSNNNJoRhPlLxFgvtb909it1WNdxTnQFipryfAPU/edit#slide=id.g7d334b12e5_0_4> please let us know if you have any questions!

-Chris


> On Feb 25, 2020, at 3:03 PM, Michael Kruse <llvm at meinersbur.de> wrote:
> 
> Looking forward to your presentation.
> 
> Michael
> 
> Am Di., 25. Feb. 2020 um 16:24 Uhr schrieb Chris Lattner <clattner at nondot.org>:
>> 
>> I’ve added notes about these Michael and Prashanth! Thanks!
>> 
>> -Chris
>> 
>>> On Feb 22, 2020, at 6:19 PM, Michael Kruse <llvm at meinersbur.de> wrote:
>>> 
>>> Am Do., 20. Feb. 2020 um 21:04 Uhr schrieb Chris Lattner via cfe-dev
>>> <cfe-dev at lists.llvm.org>:
>>>> I’m presenting a talk next Wednesday at CGO’20 about MLIR, and will be talking about some “how and why could clang and llvm use mlir” concepts.   I already hope to cover:
>>>> 
>>>> -  better separation of concerns in general.
>>>> - Make abi lowering be clang-independent
>>>> - Share OpenMP lowering across frontends, enable better openmp optimization (e.g. constant folding and hoisting across parallel loops is trivial)
>>>> - enabling high level optimizations (e.g. insert std::vector::reserve calls based on data flow analysis)
>>>> - Merging the clang CFG representation into the main flow
>>>> 
>>>> I’ll also mention some of the benefits of moving LLVM IR to MLIR - including things like multithreaded compilation, better location tracking, better modeling of invoke and other terminators, etc.
>>>> 
>>>> If anyone has any other specific things you’d like me to mention, please let me know!  I’ll be happy to share the slides with this list after the talk.  Thanks!
>>> 
>>> If the flat CFG representation is only the first step, I'd be
>>> interested in what what the end goal for representing
>>> coroutines/if/while/do/for/switch statements would, especially in
>>> combination with other statements such as
>>> goto/continue/break/return/exceptions/destructors.
>>> 
>>> Michael
>> 

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