<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Marcin,<div><br></div><div>Output of which tool do you want to diff? Are you asking about clang static analyzer(<a href="http://clang-analyzer.llvm.org/">http://clang-analyzer.llvm.org/</a>) or something else?</div><div><br></div><div>Anna.<br><div><div>On May 21, 2012, at 3:46 AM, Marcin Mirosław wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello!<br>I can't see cfe-users mailinglist so i assume cfe-dev should be good<br>place for user to ask question about clang usage. I hope i'm right.<br>I'm thinking about creating automatic tool to create clang analyse every<br>commit/every period of time. I'd like to do comparising beetwen reports<br>to know if new commits brings something unwanted in code. Ideally it<br>would be to see what errors was fixed and what wrong appears with new<br>commit. But id would be enough to see new warnings. I've got no idea how<br>to parse html to create usefull diff.<br>Is known any tool to create something like this?<br>Regards,<br>Marcin<br>_______________________________________________<br>cfe-dev mailing list<br><a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev<br></div></blockquote></div><br></div></body></html>