[RFC] The Natural Intersection of MLIR and C
We propose that a suitable subset of MLIR dialects can be directly represented in C99, and that a core Translator will produce this representation for desired usages. Our aim is to retain high-level...
View Article[RFC] The Natural Intersection of MLIR and C
Nice proposal! Something I’m not sure I perceive exactly why a new framework is necessary instead of reusing EmitC? That is: EmitC is just an emission infrastructure, the actual mapping of the...
View Article[RFC] The Natural Intersection of MLIR and C
Thank you Mehdi, There are few aspects to this RFC: first, we’d like to rise a discussion about natural intersection of MLIR and C. We are suggesting that the dialects mentioned in the RFC are good...
View Article[RFC] The Natural Intersection of MLIR and C
Hi @Diana, Thanks for a thorough proposal! I have a few high level questions: What is the intended usage or consumer of the generated C? For example, why is it important not to emit function calls? Is...
View Article[RFC] The Natural Intersection of MLIR and C
Hey @kuhar, Thank you for taking time to go through this RFC and raising important questions. There is nothing wrong with emitting functions calls. EmitC gives a freedom to call any function name and...
View Article[RFC] The Natural Intersection of MLIR and C
do you have a link to the code，can you email to me the code? thank you 1249430176@qq.com Read full topic
View Article[RFC] The Natural Intersection of MLIR and C
@xuexingtu thank you for showing an interest in this RFC. We are currently working on uploading our code for code review by the community. Currently there is our proprietary implementation which we...
View Article[RFC] The Natural Intersection of MLIR and C
You might find these two projects of interest: Rellic: decompiles LLVM modules into goto-free Clang ASTs, which can be pretty-printed to C source code. VAST: Converts C and C++ code into high-level...
View Article
