search for: g7d334b12e5_0_4

On Feb 28, 2020, at 8:56 AM, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > On 02/28, Nicholas Krause via llvm-dev wrote: >> Anyhow what is the status and what parts are we planning to move to >> MLIR in LLVM/Clang. I've not seen any discussion on that other than >> starting to plan for it. > > As far as I know, there is no

...ere, but given that Flang is already using MLIR for this, maybe it would make sense to start work there. If you’re curious, I co-delivered a talk about this recently, the slides are available here <https://docs.google.com/presentation/d/11-VjSNNNJoRhPlLxFgvtb909it1WNdxTnQFipryfAPU/edit#slide=id.g7d334b12e5_0_4>. -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200603/6290f880/attachment.html>

...ble path.  We’ll >> share the slides publicly in a few days after a couple things get >> taken care of. > > Hi all, > > Here is a link to the CGO presentation slides > <https://docs.google.com/presentation/d/11-VjSNNNJoRhPlLxFgvtb909it1WNdxTnQFipryfAPU/edit#slide=id.g7d334b12e5_0_4> (outlining > a possible path to incremental adoption of MLIR in Clang) for anyone > curious. > > -Chris Greetings, As to David Blaike's suggestion I'm merging the two threads for this discussion. The original commenters is Johannes Doefert starting with Hey,: > Hey, &g...

*TL;DR* We propose some non-trivial refactoring in Clang and LLVM to enable further work on Flang driver. *SUMMARY* We would like to start extracting the driver/frontend code from Clang (alongside the code that the driver/frontend depends on, e.g. Diagnostics) and move the components that could be re-used by non-C-based languages to LLVM. From our initial investigation we see that these