<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 3, 2015 at 9:18 AM, jahanian <span dir="ltr"><<a href="mailto:fjahanian@apple.com" target="_blank">fjahanian@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><span class=""><div>On Mar 3, 2015, at 1:28 AM, Chandler Carruth <<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>> wrote:</div><br></span><span class=""><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br>This isn't really the right way to test the driver.</div><div class="gmail_extra"><br></div><div class="gmail_extra">We usually test changes to the driver by adding a test under 'test/Driver' and using '-###' in conjunction with FileCheck to assert on the commandline formed by the driver.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Among other things, by using the driver here rather than the cc1 layer you have the following problems:</div><div class="gmail_extra"><br></div><div class="gmail_extra">- you have to carefully manage the -fobc-arc flags as you've already had to tweak in subsequent commits</div><div class="gmail_extra">- on non-x86 platforms the driver may end up producing very flawed cc1 invocations in conjunction with the hard-coded cc1 flags of '-Xclang -triple -Xclang x86_64-apple-darwin11'</div><div class="gmail_extra"><br></div><div class="gmail_extra">At least for non-x86 platforms, this is actually a breaking change and we need to revert it to get builds green again.</div></div>
</blockquote><br></span></div><div>New test in r<span style="font-family:Menlo;font-size:11px">231080</span><span style="font-family:Menlo;font-size:11px">.</span></div></blockquote></div><br>Thanks!</div></div>