<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 6, 2011, at 9:35 PM, Chandler Carruth wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Sep 6, 2011 at 9:31 PM, Argyrios Kyrtzidis <span dir="ltr"><<a href="mailto:akyrtzi@gmail.com">akyrtzi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style="word-wrap:break-word"><div><div></div><div class="h5"><div><div>On Sep 6, 2011, at 9:06 PM, Chandler Carruth wrote:</div><br><blockquote type="cite"><div class="gmail_quote">On Tue, Sep 6, 2011 at 8:55 PM, Argyrios Kyrtzidis <span dir="ltr"><<a href="mailto:akyrtzi@gmail.com" target="_blank">akyrtzi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here's an example where I'd like include stack on the note:</blockquote></div><br><div>Interesting example. Is there a heuristic here we could use to actually default some of these back on?</div><div><br></div><div>
Off the cuff, maybe show it if</div><div>- the note and the diagnostic have the same location, and</div><div>- the include stack for the diagnostic and the note differ, and</div><div>- the include stack for the note differs from that of any previous notes for that diagnostic</div>
</blockquote><br></div></div></div><div>How about show when the FileEntry of the note is the same as a previous note/warning but different FileID.</div></div></blockquote></div><br><div>Can you explain this in terms that the average user of Clang (rather than developer) would understand? I *think* i understand it, but i'm not confident.</div>
</blockquote></div><br><div>A FileEntry refers to the file in the file system but if the same source file (same FileEntry) is #include'd more than once then it gets a unique FileID each time.</div><div>So if we have 2 diagnostics that point inside the same file but inside different FileIDs it means they refer to different inclusions of the same file, thus it'd be useful to see the inclusion stacks in such a case.</div></body></html>