Hi LLVM folks,
As the sequel of my blog posts shared previously: Writing LLVM Pass in 2018 - Part I and Part II, 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
Any feedbacks are welcome 
Best Regards,
Bekket McClane
Hi Bekket,
nice article, and thank you for taking the time to write tutorials on writing passes and analyses!
The title suggests you’re talking about ‘writing passes in 2018’ which i read as new-pm passes. This part of the series is purely about legacy passes though. Is there a reason you left out new-pm passes here?
Cheers,
Philip
Hi Philip,
Sorry for the late reply.
Part 1 and 2 are talking about new PM and new AnalysisManager, feel free to check them out in links at the bottom
And I admitted the title is misleading for Part 3 and 4 of this series, where both of them are more like “one of the missing guides for LLVM / Clang”
Just kind of lazy to change the title and remove them from this series after I finished them 
Part I: https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-i-531c700e85eb
Part II: https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-ii-640f680978ec
Cheers,
Bekket