-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for LLVM 13 fuzzing #6268
Comments
Also we're seeing a different failure in |
Can confirm Rust issues - I get build failures on many (all projects I am CCed on) Rust projects. |
I'm attempting to pin the Rust toolchain to a pre-LLVM-13 version in #6288 as a temporary fix for now. |
Is this still an issue? |
@jonathanmetzman this is still an issue after rolling out clang 14 Reverting to clang13 makes suricata and rustls coverage builds succeed : Patch is
Test is
Right now, without this patch, we get Before : https://oss-fuzz-build-logs.storage.googleapis.com/log-3022ca9e-fbae-44d7-ac43-1214b857004b.txt Should we revert to clang 13 ? Only for rust projects ? |
|
I found the culprit commit in llvm : https://reviews.llvm.org/D104556 |
Cf google#6268 Latest clang-14 and clang-13 used by rust or swift have a slightly different profraw file format llvm-cov-rel is tool that will update the profraw file produced by clang-13 to one readable by clang-14 llvm-cov tools
* coverage: introduces llvm-cov-rel Cf #6268 Latest clang-14 and clang-13 used by rust or swift have a slightly different profraw file format llvm-cov-rel is tool that will update the profraw file produced by clang-13 to one readable by clang-14 llvm-cov tools * Suricata as a rust project * rust coverage: remaps every rust subdirectory in fuzz So that projects not using default fuzz_targets subdir get the good remap, and hence the good coverage report
I got a notification that the flate2 project's coverage build is failing and has the error message:
AFAIK nothing about flate2 itself has changed, but the most recent change I can think of is that the Rust compiler upgraded to LLVM 13 over the weekend. I suspect that the new LLVM version may have updated something about coverage instrumentation?
The text was updated successfully, but these errors were encountered: