zaks.anna added a comment.
Anton,
Have you investigated if we can reuse code from clang-tidy?
Also, the hope is that the python rewrite of scan-build will replace the
current scan-build in the near future. Of cause, it still needs to be tested on
Windows. I would really appreciate if you could
ayartsev added a comment.
Ping.
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ayartsev added a comment.
Ping
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ayartsev added a comment.
Upd: Forgot to remove the printHash() subroutine from libscanbuild.pm. Using it
locally for debug purpose.
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bi
ayartsev updated this revision to Diff 42762.
ayartsev added a comment.
Updated the patch following Laszlo's advises:
+ Changed config file format to YAML.
+ Dump current configuration.
+ Search for config file from the current folder and upper.
In http://reviews.llvm.org/D14629#294023, @jroelofs
xazax.hun added a comment.
Clang tidy can pass per checker configuration to the static analyzer at the
moment. I think it should not be hard to extend it.
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http:/
zaks.anna added a comment.
> And I really like how the clang-tidy guys were doing it.
It would be great if the clang static analyzer config file would be similar to
the clang-tidy one. We would avoid user confusion if they are consistent. Is
some reuse possible? Currently, when clang-tidy call
jroelofs added a comment.
Are you aware of http://reviews.llvm.org/D9600 ?
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
rizsotto.mailinglist added a comment.
I think the `scan-build` user experience would be improved by config file! And
I really like how the `clang-tidy` guys were doing it. (In case if you are not
familiar with it, copy from the help output)
Configuration files:
clang-tidy attempts to read
zaks.anna added a comment.
> > Also, how is this different from -analyzer-config?
>
>
> -analyzer-config is used to transfers a number of options to the analyzer,
> while configuration file is
> used to customize scan-build, ccc-analyzer and c++-analyzer scripts.
Could you elaborate on
ayartsev added a comment.
In http://reviews.llvm.org/D14629#288478, @jroelofs wrote:
> `CommonStuff.pm` (which could stand to have a more descriptive name,
> `libscanbuild.pm` maybe?) and `scan-build.cfg` belong in `share`.
Got it, I'll rename `CommonStuff.pm` and put it to `share` in the next
jroelofs added a comment.
Actually, now that I think about it more, `scan-build.cfg` doesn't belong in
share at all. The location of an instance of it should be read in via a
command-line argument, and it shouldn't be installed.
http://reviews.llvm.org/D14629
___
jroelofs added a comment.
Also, how is this different from `-analyzer-config`?
http://reviews.llvm.org/D14629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jroelofs added a subscriber: jroelofs.
jroelofs added a comment.
`CommonStuff.pm` (which could stand to have a more descriptive name,
`libscanbuild.pm` maybe?) and `scan-build.cfg` belong in `share`.
http://reviews.llvm.org/D14629
___
cfe-commits m
ayartsev created this revision.
ayartsev added a reviewer: zaks.anna.
ayartsev added subscribers: jordan_rose, krememek, sylvestre.ledru, cfe-commits.
A simple INI configuration file for scan-build with options - aliases to
scan-build command line arguments. This configuration file can be used to
15 matches
Mail list logo
