Displaying 6 results from an estimated 6 matches for "mcgen".
Did you mean:
cgen
2015 May 27
3
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
+1.
Could those two be subdirectories of one “Machine-Related-Stuff” directory?
E.g.,
MachineStuff/IR
MachineStuff/CodeGen
Where MachineStuff is something meaningful :).
That way, they keep a logic bound, more formal than the naming convention.
My 2c.
Q.
> On May 26, 2015, at 9:28 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On May 26, 2015, at 1:46 PM, Owen Anderson
2015 May 27
3
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
...part of the code generator.
While I would like to see this happen, is it really a good idea to put this
in the critical path of getting MIR serialized and deserialized?
>
> Also, if we’re getting crazy here, CodeGen in clang should be renamed to
> IRGen, AsmPrinter should be renamed to MCGen, and SelectionDAG should be
> replaced ;-)
>
I'm happy to actually do the CodeGen -> IRGen rename. I actually built the
change but didn't submit it because of the concerns of some out-of-tree
users of Clang. I still have all the perl scripts and such I used sitting
around.
-------...
2015 May 27
2
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
...he needed into a separately library
> pretty trivially (based on the P.O.C. patch he posted), but if it's
> not trivial he should just move on.
>
> >> Also, if we’re getting crazy here, CodeGen in clang should be
> >> renamed to IRGen, AsmPrinter should be renamed to MCGen, and
> >> SelectionDAG should be replaced ;-)
> >
> > I'm happy to actually do the CodeGen -> IRGen rename. I actually
> > built the change but didn't submit it because of the concerns of
> > some out-of-tree users of Clang. I still have all the perl scr...
2015 May 27
3
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
...hem actually including any CodeGen headers.
And all the Machine IR passes like MachineFunctionPass,
MachineFunctionAnalysis, etc. will remain in CodeGen.
Alex.
>
> >> Also, if we’re getting crazy here, CodeGen in clang should be renamed
> to IRGen, AsmPrinter should be renamed to MCGen, and SelectionDAG should be
> replaced ;-)
> >
> > I'm happy to actually do the CodeGen -> IRGen rename. I actually built
> the change but didn't submit it because of the concerns of some out-of-tree
> users of Clang. I still have all the perl scripts and such I used...
2015 May 27
0
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
...n a source file
you're *not* planning to move?
(Apparently there have been failed attempts in the past to bring
sanity here that I wasn't aware of...)
>
>
> >> Also, if we’re getting crazy here, CodeGen in clang should be renamed to IRGen, AsmPrinter should be renamed to MCGen, and SelectionDAG should be replaced ;-)
> >
> > I'm happy to actually do the CodeGen -> IRGen rename. I actually built the change but didn't submit it because of the concerns of some out-of-tree users of Clang. I still have all the perl scripts and such I used sitting around...
2015 May 27
1
[LLVMdev] RFC: Separate machine IR from lib/CodeGen into lib/MIR
...s the MIR and parser and will root out any dependencies on IR/CodeGen.
+1 for everything else BTW, not that we needed another +1.
Cheers,
Pete
>
>>
>>
>>>> Also, if we’re getting crazy here, CodeGen in clang should be renamed to IRGen, AsmPrinter should be renamed to MCGen, and SelectionDAG should be replaced ;-)
>>>
>>> I'm happy to actually do the CodeGen -> IRGen rename. I actually built the change but didn't submit it because of the concerns of some out-of-tree users of Clang. I still have all the perl scripts and such I used sitting...