Displaying 3 results from an estimated 3 matches for "094426".
2016 Mar 08
3
Deleting function IR after codegen
...think that any information that isn't being serialized in MI right now for a function could be as well. Definitely something for GlobalISel to keep in mind.
+1.
That’s basically where I would like to go with MachineModule/MachineModulePass.
http://lists.llvm.org/pipermail/llvm-dev/2016-January/094426.html
Cheers,
-Quentin
>
> I should note, a couple of issues have come up in the prototype.
> - llvm::getDISubprogram was walking the function body to find the subprogram. This is trivial to fix as functions now have !dbg on them.
>
> This is definitely worth it, please go ahead...
2016 May 12
2
Deleting function IR after codegen
...nction could be as well.
> > > Definitely something for GlobalISel to keep in mind.
> >
>
> > +1.
>
> > That’s basically where I would like to go with
> > MachineModule/MachineModulePass.
>
> > http://lists.llvm.org/pipermail/llvm-dev/2016-January/094426.html
>
> > Cheers,
>
> > -Quentin
>
> > > > I should note, a couple of issues have come up in the
> > > > prototype.
> > >
> >
>
> > > > - llvm::getDISubprogram was walking the function body to find
> > > &g...
2016 Mar 08
11
Deleting function IR after codegen
Hi all
After codegen for a given function, the IR should no longer be needed. In the AsmPrinter we convert from MI->MCInstr, and then we never go back and look at the IR during the MC layer.
I’ve prototyped a simple pass which can be (optionally) scheduled to do just this. It is added at the end of addPassesToEmitFile. It is optional so that clang can continue to leak the IR with