<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;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 17, 2017, at 1:02 PM, Chandler Carruth via llvm-commits <<a href="mailto:llvm-commits@lists.llvm.org" class="">llvm-commits@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, May 17, 2017 at 12:09 PM Daniel Berlin <<a href="mailto:dberlin@dberlin.org" class="">dberlin@dberlin.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Just to note: they weren't raised in review, they are being raised based on the performance regression discovered :)</div></blockquote><div class=""><br class=""></div><div class="">Ah good to know, I misunderstood Matthias's email.</div></div></div></div></blockquote><div>Yes they were discovered after the initial review and from a CPU target perspective the pass didn't seem to hurt.</div><div><br class=""></div><div>I answered here because I think it is convenient to have the discussion of a patch with the initial review instead of the commit mail.</div><div><br class=""></div><div>- Matthias</div></div></body></html>