<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Neil<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 17, 2017, at 6:55 AM, Neil Henning via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I did not want to make the mistake of forking LLVM/Clang - so there are a bunch of passes in there that are us undoing things that Clang has options for (if we had a SPIRV triple).</span></div></blockquote></div>Out of curiosity, can you elaborate on this? What is clang doing wrong, and why does a new triple solve it?<div class=""><br class=""></div><div class="">Also, we have loads of triple's for targets not in LLVM. You should just add one for SPIRV if you need it. I can't imagine that being controversial to folks.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Pete</div></body></html>