<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 19, 2011, at 9:07 PM, Cyril Roelandt wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; 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; font-size: medium; ">Done ! May I ask why we use a for loop in the malloc test ? I've done the same for calloc and realloc, but did not really get it.</span></blockquote></div><br><div>The original PR was 2899:</div><div><br></div><div><a href="http://llvm.org/bugs/show_bug.cgi?id=2899">http://llvm.org/bugs/show_bug.cgi?id=2899</a></div><div><br></div><div>The loops just show a typically usage of allocating memory and scribbling to the bytes. It just represents what such code might look like in practice. It isn't needed for testing this checker.</div></body></html>