<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 5 Jan 2015, at 22:30, Quentin Colombet <<a href="mailto:qcolombet@apple.com">qcolombet@apple.com</a>> wrote:</div><br><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class=""><div class="">On Jan 4, 2015, at 4:25 PM, Simon Pilgrim <<a href="mailto:llvm-dev@redking.me.uk" class="">llvm-dev@redking.me.uk</a>> wrote:</div><div class=""><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;" class=""><div class=""><br class="Apple-interchange-newline">On 4 Jan 2015, at 23:30, Chandler Carruth <<a href="mailto:chandlerc@gmail.com" class="">chandlerc@gmail.com</a>> wrote:</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">One question -- do you see any regressions that need fixing first? I don't see any, but I'm curious about others. The silence on this thread didn't inspire confidence, but perhaps its just that nothing is broken with the new stuff?</div></div></div></blockquote></div><br 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;" class=""><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;" class="">No notable regressions, I’m seeing different code but mostly for the better - although there are a number of vec256 shuffles (mostly lower/upper crossings) that are rather poor (I think Quentin raised bugs on a couple of these) - but the old system could be a lot worse.</div></div></blockquote><div><br class=""></div><div>I think Simon talks about PR21943, but this should not hold for moving forward.</div></div></blockquote><div><br></div><div>PR21138 was the one that I was thinking of but PR21943 is a regression too.</div><div><br></div><div>PR21137 covers examples of the domain crossing issues I mentioned. If people are open to putting in specific logic for shuffles in the get/set ExecutionDomain code (and not just the basic matching tables) then a fix would be relatively trivial.</div></div><br></body></html>