You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found the generator is useful for developing passes in LLVM. If I would like to add some little more supports for the generator, such as Loop pass template, choosing to register analysis pass or not. How can I test it at my local side, and probably have a patch to you.
Or if it does not meet your plan for the tool, is there a way that I can update it at my local side but not creating another similar generator? Since from my quick look of the tool, it seems like I would need to have another generator on Yeoman system if I do not merge the change in your repo. Do you have any suggestions for this?
Thanks!
The text was updated successfully, but these errors were encountered:
I'm glad that you found this tool helpful. Adding template for LoopPass looks good to me, I'll put in my TODO list. Of course, you're very welcome to send PR regarding new project template for Pass or Analysis.
To give you a really simple "getting started", you might want to read this guideline about yeoman generator development first. Then you can checkout the pass folder, which contains the sub-generator for LLVM Passes.
Currently the logic for all kinds of LLVM Passes(i.e. FunctionPass, ModulePass .etc) is put in pass/index.js. The sub-generator would choose the right template files according to user selection. All the legacy Passes shared the same template file(i.e. pass/templates/passTpl/templatePass.cpp) now, since they have nearly identical declaration structure. But IIRC, some Passes,LoopPass for example, have pretty unique Pass declarations, so you might want to create another template file.
Hi:)
I found the generator is useful for developing passes in LLVM. If I would like to add some little more supports for the generator, such as Loop pass template, choosing to register analysis pass or not. How can I test it at my local side, and probably have a patch to you.
Or if it does not meet your plan for the tool, is there a way that I can update it at my local side but not creating another similar generator? Since from my quick look of the tool, it seems like I would need to have another generator on Yeoman system if I do not merge the change in your repo. Do you have any suggestions for this?
Thanks!
The text was updated successfully, but these errors were encountered: