<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=""><div class="">Patches are best submitted to phabricator (or to the llvm-commits mailing list). See also <a href="https://llvm.org/docs/DeveloperPolicy.html#making-and-submitting-a-patch" class="">https://llvm.org/docs/DeveloperPolicy.html#making-and-submitting-a-patch</a></div><div class=""><br class=""></div><div class="">- Matthias</div><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 25, 2017, at 5:21 PM, Caballero, Diego via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi!<br class=""><br class="">I uploaded a tentative patch for the following bug in LV (<a href="https://bugs.llvm.org/show_bug.cgi?id=34965" class="">https://bugs.llvm.org/show_bug.cgi?id=34965</a>) but I have some concerns about it. I would appreciate if someone with more experience in SE/PSE can provide some feedback about current tentative fix and alternative solutions described in the comments.<br class=""><br class="">Thanks!<br class="">Diego Caballero,<br class="">Intel Vectorizer Team<br class="">_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></div></blockquote></div><br class=""></body></html>