[cfe-dev] AST Writer
Matthieu Brucher via cfe-dev
cfe-dev at lists.llvm.org
Tue Jul 10 14:49:34 PDT 2018
That's my use case, it's different than the OP, probably.
In my case, I want to generate a first pass, with a JIT (the code is
generated from another description), but the generated code could be
changed by the user in a subsequent pass.
Modifying directly the AST is not an option, try generating equations with
thousands of parameters that are solved in real time. Just no way someone
can write them efficiently in IR (that's why you have the AST to IR
I don't understand your last paragraph. If clang-format can cleanup
rewrites, why can't it reformat code from the AST? If the AST printer
writes any kind of code, why couldn't clang-format reformat it?
Le mar. 10 juil. 2018 à 22:41, David Blaikie <dblaikie at gmail.com> a écrit :
> Hmm, not sure I follow.
> Did the user write this source code? Are they going to want to change it
> later? Does it make sense for them to see the edits you're suggesting, or
> are those edits really compiler optimizations/transformations? If they're
> more the latter, then perhaps caching the LLVM IR (with these
> optimizations/transformations applied) rather than modifying the source
> would be more suitable.
> Easier to generate correctly formatted code from the AST? Not really - the
> AST printing doesn't have any particularly nuanced formatted printing.
> That's what clang-format is for (it was specifically built for doing code
> rewrites based on ASTs - where the rewrite is expressed as a textual change
> to the original source (not an AST modification) & that change is applied,
> then clang-format is used to tidy it up).
> On Tue, Jul 10, 2018 at 2:11 PM Matthieu Brucher <
> matthieu.brucher at gmail.com> wrote:
>> It's odd though, because generating code on the fly would be easier on
>> the AST than on the IR tree, if the goal is JIT and also saving the code at
>> the same time.
>> It's probably also easier also to generate properly formatted code?
>> Le mar. 10 juil. 2018 à 16:21, David Blaikie via cfe-dev <
>> cfe-dev at lists.llvm.org> a écrit :
>>> It's generally considered that the AST invariants are too subtle/complex
>>> to use AST modification and AST->source conversion reliably.
>>> Refactoring/source code modification is generally encouraged to be done via
>>> textual edits generated from source location information in the AST.
>>> On Mon, Jul 9, 2018 at 8:36 PM Ridwan Shariffdeen via cfe-dev <
>>> cfe-dev at lists.llvm.org> wrote:
>>>> I am trying to build a tool which can insert new AST nodes to a AST
>>>> tree obtained from a source code and generate the modified source code. For
>>>> example add an if condition to a given location.
>>>> I have seen examples on ReWriter which can insert text, but I want to
>>>> insert a proper AST node and generate the source code from the modified
>>>> For this purpose, I think I should be using ASTWriter and not ReWriter.
>>>> Is there any documentation I can refer on how to implement this?
>>>> Any help in this regard is highly appreciated.
>>>> cfe-dev mailing list
>>>> cfe-dev at lists.llvm.org
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org
>> Quantitative analyst, Ph.D.
>> Blog: http://blog.audio-tk.com/
>> LinkedIn: http://www.linkedin.com/in/matthieubrucher
Quantitative analyst, Ph.D.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev