<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Dec 6, 2013, at 10:54 AM, Sean Silva <<a href="mailto:silvas@purdue.edu">silvas@purdue.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><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;">Would it make sense to provide a diagnostic explaining why a loop *wasn't* vectorized (or not as requested) if it is marked with a pragma that explicitly asks for vectorization? It sounds like users would be interested in knowing that, and they really have no other way to access that information.</span><br class="Apple-interchange-newline"></blockquote></div><br><div>Yes, this would be a great feature to have, but it is unrelated to the implementation of the pragmas. </div></body></html>