<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Aug 19, 2014, at 10:37 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 5:05 PM, Jim Grosbach <span dir="ltr"><<a href="mailto:grosbach@apple.com" target="_blank">grosbach@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Note that it’s not exactly equivalent to enabling -march=core-avx2. It’s really close, but not 100% the same.</blockquote>
</div><br>What is the difference?</div></div></blockquote><div><br></div><div>The x86_64h triple is specifically targeted for a subclass of Haswell features. For instance, IIRC, unlike core-avx2, it does not have the AES feature.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"> and why? It seems really confusing to have this divergence, or to be unable to replicate the *exact* behavior of this (very weird, and IMO *bad* triple) with the standard triple of 'x86_64-...' and an '-march' flag.</div></div></blockquote><div><br></div><div>This is basically a mix of x86_64, -march, and a few target features.</div><div><br></div><div>Cheers,</div><div>Q. </div><br><blockquote type="cite"><div dir="ltr">
</div>
_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote></div><br></body></html>