<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 7, 2009, at 3:44 PM, Daniel Dunbar wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Apr 7, 2009 at 11:55 AM, Mike Stump <span dir="ltr"><<a href="mailto:mrs@apple.com">mrs@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Apr 7, 2009, at 8:53 AM, Daniel Dunbar wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Towards that end (and the direction we have been headed), the idea is to make clang do the *maximum* of translation<br> </blockquote> <br></div> I envision a world that doesn't have clang calling out to a clang-cc; one where we don't pay for the extra fork and exec. I just don't see the advantage.<br> </blockquote></div><br><div>Yes; I was talking about the same world. This is why we want to move all complicated argument handling to one place, the driver.</div><div></div></blockquote></div><br><div>FYI:</div><div><a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090406/076104.html">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090406/076104.html</a></div><div><br></div><div>Lets drop this or take it offline.</div><div><br></div><div>-Chris</div></body></html>