3 ms·
> llvm already has instrumentation The Go toolchain actually supports emitting instrumentation for LLVM's libFuzzer with -gcflags=all=-d=libfuzzer. > therefor
by smasher164 5y ago
> llvm already has instrumentation
The Go toolchain actually supports emitting instrumentation for LLVM's libFuzzer with -gcflags=all=-d=libfuzzer.
> therefor the language has to add more
Okay, and so? If this ends up making fuzzing more popular and easy-to-use, I frankly don't care if it was added as a library or deeply integrated into the toolchain.
- staticassertion 5y ago> The Go toolchain actually supports emitting instrumentation for LLVM's libFuzzer with -gcflags=all=-d=libfuzzer. Sweet, that's a smart approach. > Okay, and so? If this ends up making fuzzing more popular and easy-to-use, I frankly don't care if it was added as a library or deeply integrated into the toolchain. I don't care either because I don't write Go, so just the fact that it's supported is nice for me since it encourages this in languages I do care about. But if I were a go developer I might care a lot about how my language evolves, what's built in, what's a library, what the capabilities are, what tools I can integrate with, etc. It sounds like they've done a pretty good job with regards to this implementation though, happy to see it.