<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 Jan 22, 2015, at 11:03 AM, Filipe Cabecinhas <<a href="mailto:filcab@gmail.com" class="">filcab@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">What would be the difference between shelling out to clang -cc1as or simply doing a no-op on -no-integrated-as?<div class=""><br class=""></div><div class="">We could also start not allowing clang (on OS X) to emit directives by default if the latest Xcode-shipped clang doesn't handle them. That is: Maybe we should say what the “ground truth” for MachO/OSX is, and which tools outside of llvm we should try to be compatible with.</div><div class=""><br class=""></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">This whole problem is due to clang emitting ".macosx_version_min" and other directives by default, and the latest Xcode-provided clang/as -q not handling them.</div></div></div></blockquote><div><br class=""></div>It’s far, far bigger than that. clang uses many assembly constructs that the non-integrated assembler doesn’t support. Passing clang generated assembly files into the cctools assembler is not supported and hasn’t been for a quite a while. The current cctools as(1) is deprecated.</div><div><br class=""></div><div>-Jim</div><div><br class=""><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">Rafael: Yes, AFAICT that is the only case that is broken (and without the -c, but that's basically the same case).<br class=""><div class=""><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"> Filipe<br class=""></div></div>
<br class=""><div class="gmail_quote">On Thu, Jan 22, 2015 at 10:56 AM, Rafael Espíndola <span dir="ltr" class=""><<a href="mailto:rafael.espindola@gmail.com" target="_blank" class="">rafael.espindola@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> If cctools as isn't supported, perhaps we should make -no-integrated-as<br class="">
> shell out to `clang -cc1as` on Darwin. Users may be relying on<br class="">
> -no-integrated-as implying cctools as quirks, though.<br class="">
<br class="">
</span>It is probably a good idea. Since cctools' as can't handle clang<br class="">
output, the only use case that might be broken by the change is "clang<br class="">
-c -no-integrated-as foo.s", no?<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
Cheers,<br class="">
Rafael<br class="">
_______________________________________________<br class="">
llvm-commits mailing list<br class="">
<a href="mailto:llvm-commits@cs.uiuc.edu" class="">llvm-commits@cs.uiuc.edu</a><br class="">
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank" class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br class="">
</div></div></blockquote></div><br class=""></div></div></div></div>
_______________________________________________<br class="">llvm-commits mailing list<br class=""><a href="mailto:llvm-commits@cs.uiuc.edu" class="">llvm-commits@cs.uiuc.edu</a><br class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits<br class=""></div></blockquote></div><br class=""></body></html>