[llvm-dev] -sanitizer-coverage-prune-blocks=true and LibFuzzer
Mehdi Amini via llvm-dev
llvm-dev at lists.llvm.org
Wed Sep 21 13:37:20 PDT 2016
> On Sep 21, 2016, at 1:25 PM, Kostya Serebryany <kcc at google.com> wrote:
> On Wed, Sep 21, 2016 at 12:58 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote:
>> On Sep 21, 2016, at 12:56 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote:
>> On Wed, Sep 21, 2016 at 12:32 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote:
>>> On Sep 21, 2016, at 9:36 AM, Kostya Serebryany via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>> (btw, I'd prefer libfuzzer at googlegroups.com <mailto:libfuzzer at googlegroups.com> for such discussions, please start new topics there)
>> You mean a LLVM library has a separate mailing-list? Why?
>> Because the topic is very separate.
> Can you clarify?
> I thought is was about the development/debug/evolution/usability of http://llvm.org/svn/llvm-project/llvm/trunk/lib/Fuzzer/ <http://llvm.org/svn/llvm-project/llvm/trunk/lib/Fuzzer/>
> Yes, and this topic is substantially different from most other topics discussed on llvm-dev.
How so? If discussion on the development of a LLVM sub-library does not belong to llvm-dev, I wonder if the library belong to LLVM in the first place (add to this that libFuzzer does not use anything else in LLVM…).
> We also have separate maliing lists for asan/tsan/msan
Is it for more anything else than historical reasons?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev