Sylvestre Ledru via llvm-dev
2019-Sep-14 17:58 UTC
[llvm-dev] [GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report
Hello, Le 29/08/2019 à 01:02, Artem Dergachev a écrit :> Yay thx! > > Sylvestre, is there anything i can help you with in order to get the reports page back up?Sorry, it took me a while to get that back but here is the report of r371718: https://llvm.org/reports/scan-build/> I'd also indeed love to spam people with warnings that they introduced, even if in the form of a weekly summary. We already have scripts that compare scan-build outputs, but we mostly use them for testing the analyzer itself.sure, it would be great to have. Do you have a way to do that currently ? For Firefox, I have been using codechecker for this: https://github.com/Ericsson/codechecker Sylvestre
Simon Pilgrim via llvm-dev
2019-Sep-15 15:50 UTC
[llvm-dev] [GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report
Awesome - thank you for getting it back up and running - the warning count has gone up a bit while it was away! On 14/09/2019 18:58, Sylvestre Ledru wrote:> Hello, > > Le 29/08/2019 à 01:02, Artem Dergachev a écrit : >> Yay thx! >> >> Sylvestre, is there anything i can help you with in order to get the >> reports page back up? > > Sorry, it took me a while to get that back but here is the report of > r371718: > https://llvm.org/reports/scan-build/ > >> I'd also indeed love to spam people with warnings that they >> introduced, even if in the form of a weekly summary. We already have >> scripts that compare scan-build outputs, but we mostly use them for >> testing the analyzer itself. > sure, it would be great to have. Do you have a way to do that currently ? > For Firefox, I have been using codechecker for this: > https://github.com/Ericsson/codechecker > > Sylvestre
Dániel Krupp via llvm-dev
2019-Sep-16 09:51 UTC
[llvm-dev] [cfe-dev] [GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report
Thanks Sylvestre, Could you pls send us the link to the Firefox results? Regards, Daniel -----Original Message----- From: cfe-dev <cfe-dev-bounces at lists.llvm.org> On Behalf Of Simon Pilgrim via cfe-dev Sent: Sunday, September 15, 2019 05:51 PM To: Sylvestre Ledru <sylvestre at debian.org>; Artem Dergachev <noqnoqneo at gmail.com>; Csaba Dabis <dabis.csaba98 at gmail.com>; Gábor Horváth <xazax.hun at gmail.com>; Zoltan Porkolab <gsd at inf.elte.hu>; llvm-dev at lists.llvm.org; cfe-dev at lists.llvm.org; Devin Coughlin <dcoughlin at apple.com> Subject: Re: [cfe-dev] [GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report Awesome - thank you for getting it back up and running - the warning count has gone up a bit while it was away! On 14/09/2019 18:58, Sylvestre Ledru wrote:> Hello, > > Le 29/08/2019 à 01:02, Artem Dergachev a écrit : >> Yay thx! >> >> Sylvestre, is there anything i can help you with in order to get the >> reports page back up? > > Sorry, it took me a while to get that back but here is the report of > r371718: > https://protect2.fireeye.com/url?k=c8cbf2bc-94425d26-c8cbb227-0cc47ad9 > 3e74-c94f79b6ad6a0e26&q=1&u=https%3A%2F%2Fllvm.org%2Freports%2Fscan-bu > ild%2F > >> I'd also indeed love to spam people with warnings that they >> introduced, even if in the form of a weekly summary. We already have >> scripts that compare scan-build outputs, but we mostly use them for >> testing the analyzer itself. > sure, it would be great to have. Do you have a way to do that currently ? > For Firefox, I have been using codechecker for this: > https://protect2.fireeye.com/url?k=4db9f4ee-11305b74-4db9b475-0cc47ad9 > 3e74-1b0a0857fd763906&q=1&u=https%3A%2F%2Fgithub.com%2FEricsson%2Fcode > checker > > Sylvestre_______________________________________________ cfe-dev mailing list cfe-dev at lists.llvm.org https://protect2.fireeye.com/url?k=264b506e-7ac2fff4-264b10f5-0cc47ad93e74-81e4b3031353bc62&q=1&u=https%3A%2F%2Flists.llvm.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fcfe-dev