<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 29, 2013, at 2:44 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">So, I'd like Andy to chime in on whether he's comfortable with this use of TTI. I think I'm OK with it, but it's a borderline case.</div></blockquote><div><br></div><div>I don’t think this makes it harder to do the right thing later—move the whole partial unrolling pass after CGSCC. So OK for now.</div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Second, I think essentially only the LoopVectorizer should use this to drive its partial unrolling. This is both because it has added information about when the cost is low (ILP) and when the cost is unusually high. Finally, it should happen at the same phase of the optimizer IMO (IE, it shouldn't drastically influence the behavior of the inliner). While the LoopVectorizer is currently inside the CGSCC pass pipeline, Nadav is working on moving it to live after that completes.</div></blockquote></div><br><div>Yep…</div><div><br></div><div>-Andy</div></body></html>