search for: irgenfunction

> I really dislike that all the files and classes in the MC library > start with MC. This is c++, not c :( Same here. > > - Michael Spencer Cheers, Rafael

Hi, I think it's an awesome idea to make sure all names are logical. It is an essential feature of a good API to have logical naming :) > I really dislike that all the files and classes in the MC library > start with MC. This is c++, not c :( On a similar note, all the classes in clang/CodeGen are prefixed with CG or even CodeGen, could those be renamed as well? And speaking of the

...I really dislike that all the files and classes in the MC library >> start with MC. This is c++, not c :( > > On a similar note, all the classes in clang/CodeGen are prefixed with > CG or even CodeGen, could those be renamed as well? Yes. For example, CodeGenFunction would become IRGenFunction. CGCall.cpp would become... probably either GenCall.cpp or IRGenCall.cpp, with my preference being the shortest that's still unambiguous throughout the project, which I think means Gen*. > And speaking of the clang codegenerator, I as a llvm newbie was > confused by the ModuleBuilder.h/....

On Thu, Nov 14, 2019 at 9:59 AM Reid Kleckner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think the idea of more expanded frontend support library makes sense. > The main use case that I've heard for such a library is to help frontends > generate LLVM IR that interfaces with the local native C ABI. > I agree it would be good to have a library for shared frontend