<html><body bgcolor="#FFFFFF"><div>Yes, the diagnostics you changed s<span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">ound good. I'm just asking for the next step :)</span></div><div><br><div>-Chris</div></div><div><br>On Apr 6, 2011, at 11:50 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div class="gmail_quote">On Wed, Apr 6, 2011 at 11:13 PM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com"><a href="mailto:clattner@apple.com">clattner@apple.com</a></a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Looks good to me. Please also change "is possibly uninitialized" to "may be uninitialized" while you're at it, thanks!</blockquote></div><br><div>On some further discussion, I think I understand what these messages were aiming at: the 'possibly' isn't about whether we've proven there to be a path leading to uninitialized use, but the fact that we haven't proven *all* paths to cause an uninitialized use....</div>
<div><br></div><div>I still want some different wording here. Do you think the wording I proposed in the patch is actually OK for this? Is there a better way to phrase it?</div>
</div></blockquote></body></html>