<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 14, 2015, at 10:46 AM, Pete Cooper <<a href="mailto:peter_cooper@apple.com" class="">peter_cooper@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span 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; float: none; display: inline !important;" class="">If R600 already has a regalloc solution to this problem, shouldn’t we see if this proposal will remove the need for SIFixSGPRLiveRanges.cpp before we start committing anything?</span></div></blockquote></div><div class=""><br class=""></div>SIFixSGPRLiveRanges solves a related but not equivalent problem. If you read the block comment at the top of the file, SI would require live range fixups on the example used here even if the code motion were prevented by a convergent attribute.<div class=""><br class=""></div><div class=""><div class=""><br class=""></div><div class="">—Owen</div></div></body></html>