<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 21, 2013, at 12: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">On Mon, Jan 21, 2013 at 11:49 AM, Andrew Trick <span dir="ltr"><<a href="mailto:atrick@apple.com" target="_blank" class="cremed">atrick@apple.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Moving to llvmdev...<br>
<div class="im"><br>
On Jan 21, 2013, at 11:37 AM, Nadav Rotem <<a href="mailto:nrotem@apple.com" class="cremed">nrotem@apple.com</a>> wrote:<br>
<br>
> Hi Manish,<br>
><br>
> Thank you for looking at this. Recently opt started using the "-mtriple" command line flag to initialize the TargetMachine for IR-level transformations that use it. Currently only the following passes are using this feature: LSR, LowerSwitch, BBVectorizer and LoopVectorizer. If you look at the tests in LoopVectorize you will see that the target-dependent tests are in target-dependent directories.<br>
<br>
</div>The tests in the platform directories are fine. The question is what to do about all the tests in target-independent directories that have "target triple" in the bitcode. These tests don't use -mtriple. Instead, their behavior changes in subtle ways depending on which targets are built. It's certainly a confusing situation.<br>
</blockquote><div><br></div><div style="">My proposed resolution:</div><div style="">- If the tests are target independent, delete the triple.<br></div><div style="">- If they aren't, sink them to a target-specific subdirectory so they're skipped in the absence of the target being built.</div></div></div></div></blockquote><div><br></div><div>Filed <a href="http://llvm.org/pr15025">llvm.org/pr15025</a>.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div style="">- Make a triple an error if there is not support for that target.</div></div></div></div></blockquote><div><br></div>Filed <a href="http://llvm.org/pr15026">llvm.org/pr15026</a>.<blockquote type="cite">
</blockquote></div><div><br></div><div><div>I assume opt should completely ignore target triple when -mtriple is provided, potentially bypassing the error.</div><div><br></div><div>-Andy</div></div><br></body></html>