search for: lowerform

...; > *nod* I'd like to do something about the AsmPrinter anyhow. > > >> >> - Introduce new APIs to have a clearer separation between: >> - Legalization (setOperationAction, etc.) >> - Cost/Combine related (isXXXFree, etc.) >> - Lowering related (LowerFormal, etc.) >> - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? >> >> Probably :) >> >> As far as the prototype I think you also need to address a few additional things: >> >> a) Calls >> Calls are...

...d of M1 * - Handling of aggregate types during the translation. - Lowering of switches. - What about Module pass for Machine pass? - Introduce new APIs to have a clearer separation between: - Legalization (setOperationAction, etc.) - Cost/Combine related (isXXXFree, etc.) - Lowering related (LowerFormal, etc.) - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? Thanks, -Quentin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151118/b483435a/attachment-...

...d to function but module, therefore it seems to make sense to introduce a concept of MachineModulePass. > > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? > > Probably :) > > As far as the prototype I think you also need to address a few additional things: > > a) Calls > Calls are probably the most important part...

...gate types during the translation. > - Lowering of switches. > - What about Module pass for Machine pass? > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? > > Thanks, > -Quentin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160107/9b038...

...gate types during the translation. > - Lowering of switches. > - What about Module pass for Machine pass? > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? > > Thanks, > -Quentin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160111/fe104...

...gate types during the translation. > - Lowering of switches. > - What about Module pass for Machine pass? > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to > select any valid LLVM IR”? > > Thanks, > > -Quentin > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://li...

...gate types during the translation. > - Lowering of switches. > - What about Module pass for Machine pass? > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? > > Thanks, > -Quentin > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm...

...gate types during the translation. > - Lowering of switches. > - What about Module pass for Machine pass? > - Introduce new APIs to have a clearer separation between: > - Legalization (setOperationAction, etc.) > - Cost/Combine related (isXXXFree, etc.) > - Lowering related (LowerFormal, etc.) > - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? > > Thanks, > -Quentin > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lis...

...anslation. >> - Lowering of switches. >> - What about Module pass for Machine pass? >> - Introduce new APIs to have a clearer separation between: >> - Legalization (setOperationAction, etc.) >> - Cost/Combine related (isXXXFree, etc.) >> - Lowering related (LowerFormal, etc.) >> - What is the contract with the backends? Is it still “should be able to select any valid LLVM IR”? >> >> Thanks, >> >> -Quentin >> >> >> _______________________________________________ >> LLVM Developers mailing list >> l...