Document that libFuzzer supports Windows, how to get it,
and its limitations.
I don't understand LLVM's release process to know when the official LLVM build goes up and what parts of libFuzzer on Win it will support.
any reliable bot will do.
This one, ... hm, doesn't seem reliable.
Last build passed two days ago :(
A separate bot would be nice if you expect a high rate of changes (and breakages) on windows
I am taking steps to add it to sanitizer-windows here, which is super fast and reliable (for a sanitizer bot =P):
I think this doc change is ready to go as is. It reflects the state of the very near future.
We'd have to merge this to the 8.0 branch, but committing as normal is the first step. We'd also want to put a release note in llvm/docs/ReleaseNotes.rst on the 8.0 branch. @hans is the person to ask about this.
To follow-up, check-fuzzer passed on sanitizer-windows:
[99/102] Running Fuzzer unit tests llvm-lit.py: C:/b/slave/sanitizer-windows/build/llvm.src/projects/compiler-rt/test/fuzzer/lit.cfg:32: note: lsan feature unavailable llvm-lit.py: C:/b/slave/sanitizer-windows/build/llvm.src/projects/compiler-rt/test/fuzzer/lit.cfg:39: note: msan feature unavailable llvm-lit.py: C:/b/slave/sanitizer-windows/build/llvm.src/projects/compiler-rt/test/fuzzer/lit.cfg:57: note: linux feature unavailable -- Testing: 36 tests, 16 threads -- Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. Testing Time: 0.92s Expected Passes : 36
Do we need more targets?
Sounds good to me. I'll merge this when it lands (maybe I'll drop the part about Clang 9), then please write something for the release notes. You can either send a patch for docs/ReleaseNotes.html on the branch, or just write some text and I'll add it.
Thanks for pointing this out. Judging from the current docs, I think single backticks for non-links just does italics.
I'm not sure what's going on with the documentation page and why hit hasn't updated though.