On Thu, Apr 12, 2012 at 3:28 PM, Jonathan Wakely <jwakely....@gmail.com> wrote: > On 12 April 2012 22:53, Xinliang David Li wrote: >> yes .. > > Excellent, thanks, and thanks for the link to the pdf, I hadn't seen > it before and GCC does do pretty poorly with those examples.
The talk was given pretty recently .. David > > >> thanks, >> >> David >> >> On Thu, Apr 12, 2012 at 2:51 PM, Jonathan Wakely <jwakely....@gmail.com> >> wrote: >>> On 12 April 2012 22:32, Xinliang David Li wrote: >>>> Thanks for preparing the wiki page. I have looked at the examples from >>>> this slide: http://ecn.channel9.msdn.com/events/GoingNative12/GN12Clang.pdf >>>> with trunk gcc. In some cases, gcc's warning matches that of clang but >>>> in majority of cases, gcc either emits no warnings or worse ones. The >>>> warnings in the comments are from clang. One possible advantage of >>>> clang is that adding new warnings is relatively easier. >>> >>> Noone will add them to GCC unless someone requests them. You're in >>> the process of creating bugzilla reports for those issues, right?
