<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 Jul 16, 2013, at 5:51 PM, Eli Friedman <<a href="mailto:eli.friedman@gmail.com">eli.friedman@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="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;">On Tue, Jul 16, 2013 at 5:21 PM, Quentin Colombet <<a href="mailto:qcolombet@apple.com">qcolombet@apple.com</a>> wrote:<br><blockquote type="cite">** Advices Needed **<br><br>1. Decide whether or not we want such capabilities (if we do not we may just<br>add sporadically the support for a new warning/group of warning/error).<br>2. Come up with a plan to implement that (assuming we want it).<br></blockquote><br>The frontend should be presenting warnings, not the backend; adding a<br>hook which provides the appropriate information shouldn't be too hard.<br>Warnings coming out of the backend are very difficult to design well,<br>so I don't expect we will add many. Also, keep in mind that the<br>information coming out of the backend could be used in other ways; it<br>might not make sense for the backend to decide that some piece of<br>information should be presented as a warning. (Consider, for example,<br>IDE integration to provide additional information about functions and<br>loops on demand.)</div></blockquote><br></div><div>I think we definitely need this. In fact, I tried adding something simple earlier this year but gave up when I realized that the task was bigger than I expected. We already have a hook for diagnostics that can be easily extended to handle warnings as well as errors (which is what I tried earlier), but the problem is that it is hardwired for inline assembly errors. To do this right, new warnings really need to be associated with warning groups so that can be controlled from the front-end.</div><div><br></div><div>I agree with Eli that there probably won’t be too many of these. Adding a few new entries to clang’s diagnostic .td files would be fine, except that the backend doesn’t see those. It seems like we will need something in llvm that defines a set of “backend diagnostics”, along with a table in the frontend to correlate those with the corresponding clang diagnostics. That seems awkward at best but maybe it’s tolerable as long as there aren’t many of them.</div><div><br></div><div>—Bob</div></body></html>