Skip to content

Unknown pass name 'sancov' #192

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

Closed
smoelius opened this issue Sep 27, 2021 · 5 comments · Fixed by #193 or #197
Closed

Unknown pass name 'sancov' #192

smoelius opened this issue Sep 27, 2021 · 5 comments · Fixed by #193 or #197

Comments

@smoelius
Copy link
Member

rust-fuzz/cargo-fuzz#276

afl.rs suffers from this issue as well:

-C passes=sancov \

-C passes=sancov \

There seem to be at least two options:

  • Wait and see what cargo-fuzz does.
  • Charge ahead and implement a fix for the latest nightly.

I don't have a strong opinion. Does anyone else?

@smoelius
Copy link
Member Author

cargo-fuzz has published a fix: rust-fuzz/cargo-fuzz#277

@charlesxsh
Copy link

This error is caused by new LLVM pass manager, which sancov has a new name called "sancov-module". The fix should check llvm version to decide which name should be used.

@charlesxsh
Copy link

charlesxsh commented Oct 1, 2021

@smoelius The workaround could be passing -Znew-llvm-pass-manager=no to avoid new LLVM pass manager.
If running in Cargo, it will be RUSTFLAGS="-Znew-llvm-pass-manager=no" cargo ...

197g added a commit to 197g/image that referenced this issue Oct 2, 2021
Work around an issue due to new pass-manager, as mentioned here:
<rust-fuzz/afl.rs#192 (comment)>

This affords us some time (until LLVM 14 or 15 iirc) for a more
permanent fix to appear upstream.
197g added a commit to 197g/image that referenced this issue Oct 2, 2021
Work around an issue due to new pass-manager, as mentioned here:
<rust-fuzz/afl.rs#192 (comment)>

This affords us some time (until LLVM 14 or 15 iirc) for a more
permanent fix to appear upstream.
@smoelius
Copy link
Member Author

smoelius commented Oct 5, 2021

@smoelius The workaround could be passing -Znew-llvm-pass-manager=no to avoid new LLVM pass manager. If running in Cargo, it will be RUSTFLAGS="-Znew-llvm-pass-manager=no" cargo ...

@charlesxsh I'm sorry for having gotten sidetracked with #193. But your suggestion was very helpful, and I did actually make use it. Thank you very much.

@smoelius
Copy link
Member Author

rust-lang/rust@150bd8b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants