<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 5, 2015, at 2:56 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com" class="">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Mar 5, 2015 at 2:51 PM, Pete Cooper <span dir="ltr" class=""><<a href="mailto:peter_cooper@apple.com" target="_blank" class="">peter_cooper@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><span class=""><blockquote type="cite" class=""><div class="">On Mar 5, 2015, at 2:47 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com" target="_blank" class="">chandlerc@google.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Mar 5, 2015 at 2:46 PM, Pete Cooper <span dir="ltr" class=""><<a href="mailto:peter_cooper@apple.com" target="_blank" class="">peter_cooper@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Yeah, I agree that layering is an issue.</div><div class=""><br class=""></div><div class="">The current pass code is in lib/IR, which I think is libCore. There’s no fundamental reason why your code couldn’t also live there right now. Its linked against everything you mentioned already.</div></blockquote><div class=""><br class=""></div><div class="">Wait, you've lost me.</div></div></div></div></div></blockquote></span>I’m talking about what if you didn’t create a new library. I think you’re talking about the relationship between the new libPasses and other libraries. Otherwise i’m lost too :)</div><div class=""><br class=""></div><div class="">I was saying that if you didn’t create a new library, then I assumed the new PM code could live in libCore next to the current PM code. And then everything just depends on libCore as they currently do.</div></blockquote></div><br class=""></div><div class="gmail_extra">No no, that's the problem. Everything depends on libCore. Including libTransforms, libTarget, etc.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">the code i've got in Passes right now depends on code in the target library and in the transforms and analysis library. It can't do that from libCore without creating a cycle.</div></div></div></blockquote>Ah, i see. Ouch!<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""></div><div class="gmail_extra">So we have:</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">parsePassPipeline -> SROA (libTransforms) -> PassManager (IR / Core)</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">If we put parsePassPipeline in Core, we form a cycle.</div></div>
</div></blockquote>Gotcha.</div><div><br class=""></div><div>So how much of this is going to be optional? If I create a dylib, can I opt out of parsePassPipeline (export list probably), and therefore not have to link all the passes? I don’t want to have to carry around passes I know I don’t need.</div><br class=""></body></html>