search for: mshockwave

Hi LLVM folks, As the sequel of my blog posts shared previously: Writing LLVM Pass in 2018 - [Part I](https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-i-531c700e85eb <https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-i-531c700e85eb> ) and [Part II](https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-ii-640f680978ec <https://medium.com/@mshockwave/writing-llvm-pass-in-2018-part-ii-640f6...

...t; among scope children which would be encountered pretty early. So sometimes threads are fired, but the correct instruction is actually immediately selected after that. Thus lots of time is wasted on joining threads. Here is our working repository and diff with 3.9 release: https://bitbucket. org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff <https://bitbucket.org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff> I don't think the current state is ready for code reviewing since there is no significant speedup. But it's very welcome for folks to discuss ab...

...-help' opt-4.0: Did you mean '-loops’? 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...

...ldren which would be encountered pretty early. So sometimes threads are fired, but the correct instruction is actually immediately selected after that. Thus lots of time is wasted on joining threads. >> >> Here is our working repository and diff with 3.9 release: https://bitbucket.org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff  <https://bitbucket.org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff> >> I don't think the current state is ready for code reviewing since there is no significant speedup. But it's very welcome for folks to...

...ldren which would be encountered pretty early. So sometimes threads are fired, but the correct instruction is actually immediately selected after that. Thus lots of time is wasted on joining threads. >> >> Here is our working repository and diff with 3.9 release: https://bitbucket.org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff  <https://bitbucket.org/mshockwave/hydra-llvm/branches/compare/master%0D3.9-origin#diff> >> I don't think the current state is ready for code reviewing since there is no significant speedup. But it's very welcome for folks to...

...otential performance issue(Sorry I can't provide concrete evidence, any benchmark result is welcome) but also non-standard. Before std::shared_mutex in C++17 got fully adopt by LLVM codebase, I think we can use std::atomic + std::conditional_variable approach like this: https://gist.github.com/mshockwave/b314eb78d4019e7e106e705e864e0398 to power RWMutex. -- Bekket McClane Department of Computer Science, National Tsing Hua University -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161031/6c418aa7/attachment....

Hi all, Apparently some people had trouble joining today. I also had trouble using the attendee ID provided by webex. I've canceled the meeting series and will be scheduling a new one with an updated link. Please remember to update your calendars with the new invite. My apologies to those who couldn't join today, and to everyone for the churn. Today's Meeting Minutes: