search for: d44cd0c2c354

...ng-llvm-pass-in-2018-part-ii-640f680978ec> ), I’m going to talk about how to integrate your Pass into the LLVM source tree. Which, in my point of view, would be especially useful for LLVM developers. Here is the link: [Part III](https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-iii-d44cd0c2c354 <https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-iii-d44cd0c2c354> ) Any feedbacks are welcome :-) Best Regards, Bekket McClane -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180826/0bb...

...3) I tried to invoke custom LLVM passes from clang rather than opt. I followed instructions from several articles like https://www.cs.cornell.edu/~asampson/blog/llvm.html <https://www.cs.cornell.edu/~asampson/blog/llvm.html> https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-iii-d44cd0c2c354 <https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-iii-d44cd0c2c354> and registered the pass to clang’s workflow with legacy pass manger. But it raises segmentation fault errors. What is a recommended way to register custom passes to clang directly? Thanks in advance. Best, Kiho...