<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 9, 2009, at 4:33 PM, Zhongxing Xu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">2009/11/10 Ted Kremenek <<a href="mailto:kremenek@apple.com">kremenek@apple.com</a>>:<br><blockquote type="cite">Hi Zhongxing,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Very nice I vaguely recall we use to do this check, albeit not as directly.<br></blockquote><br>Perhaps in EvalLocation().<br><br><blockquote type="cite"> How do we want to handle cases like PR 5272<br></blockquote><blockquote type="cite">(<a href="http://llvm.org/bugs/show_bug.cgi?id=5272">http://llvm.org/bugs/show_bug.cgi?id=5272</a>)?<br></blockquote><br>Leave it as a false positive.<br><br><blockquote type="cite">Using hardcoded addresses is<br></blockquote><blockquote type="cite">fine in certain circumstances.<br></blockquote><br>Definitely. So I see this kind of check as some kind of guide to the<br>programmer, not as some absolute judger of the code. False positives<br>are allowed. There should not be too much.</span></blockquote></div><br><div>Makes sense. Eventually we should provide a mechanism to silence false positives of this nature.</div></body></html>