On Mon, Jan 4, 2016 at 7:39 PM, Kostya Serebryany wrote:
> Nice!
> is a fuzzer for clang-tidy possible/
>
Should be no more difficult than clang-fuzzer.
> desirable?
>
It might be useful to find crashes in clang-tidy earlier than we feed a ton
of sources to it. Not sure how
On Tue, Jan 5, 2016 at 9:01 AM, Alexander Kornienko
wrote:
> On Mon, Jan 4, 2016 at 7:39 PM, Kostya Serebryany wrote:
>
>> Nice!
>> is a fuzzer for clang-tidy possible/
>>
>
> Should be no more difficult than clang-fuzzer.
>
Let's do it then?
>
>
>>
Nice!
is a fuzzer for clang-tidy possible/desirable?
similar to what we have for clang and clang-format
(tools/clang-format/fuzzer, ./tools/clang-fuzzer)
On Tue, Dec 29, 2015 at 8:14 AM, Alexander Kornienko via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Author: alexfh
> Date: Tue Dec 29
On Tue, Dec 29, 2015 at 5:22 PM, Benjamin Kramer
wrote:
> On Tue, Dec 29, 2015 at 5:14 PM, Alexander Kornienko via cfe-commits
> wrote:
> > Author: alexfh
> > Date: Tue Dec 29 10:14:38 2015
> > New Revision: 256562
> >
> > URL:
Author: alexfh
Date: Tue Dec 29 10:14:38 2015
New Revision: 256562
URL: http://llvm.org/viewvc/llvm-project?rev=256562=rev
Log:
[clang-tidy] Fix a use-after-free bug found by asan
Modified:
clang-tools-extra/trunk/clang-tidy/readability/SimplifyBooleanExprCheck.cpp
Modified:
On Tue, Dec 29, 2015 at 5:14 PM, Alexander Kornienko via cfe-commits
wrote:
> Author: alexfh
> Date: Tue Dec 29 10:14:38 2015
> New Revision: 256562
>
> URL: http://llvm.org/viewvc/llvm-project?rev=256562=rev
> Log:
> [clang-tidy] Fix a use-after-free bug found by asan