<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 Dec 31, 2012, at 11:57 AM, Benjamin Kramer <<a href="mailto:benny.kra@gmail.com">benny.kra@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">I'm not entirely sure why this is the case, the target specific stuff for opt is still very new, but at the moment you have to explicitly set a triple for opt so it can access target-specific bits to estimate the cost of vectorization.</span></blockquote></div><br><div>I think that this is a good opportunity to discuss this topic. At the moment 'opt' does not use the triple that is found in the module in order to initialize the backend and the backend related analysis passes. It relies on the '-mtriple' command line flag. LLC on the other hand uses the host triple. I see the following options:</div><div><br></div><div>1. 'opt' does not initialize the backend passes unless '-mtriple' is used. (the current option)</div><div>2. 'opt' grabs the triple from the bit code file and uses it to initialize the backend passes.</div><div>3. 'opt' gets the default target triple (like llc).</div><div><br></div><div>I think that Nick said that he prefers #2.</div><div><br></div><div>Nadav </div></body></html>