-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Consider not running the verifier in non-debug builds #3554
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
Comments
no-verify is already a debugging option, so I assume the compiler just needs some simple logic to add this to the driver in non-debug builds. |
Related #3615. Nominating production-ready. |
just a bug, removing milestone/nomination. |
Triage: I assume that the verifier is no-opt
86s for the entire rustc invocation.
|
Is this still relevant? |
Yes, it's still relevant. I think we do want to keep running this for now though. |
Triage: -Z time-llvm-passes 2>&1 | grep "Module Verifier"
-O -Z time-llvm-passes 2>&1| grep "Module Verifier"
tested with wtftw, takes 17s total on my machine |
It's a small improvement. Still doesn't seem worth turning it off to me. Are we ever going to want to turn off the LLVM module verifier? Can we close this issue? cc @rust-lang/compiler |
You snooze you lose! |
document unofficially supported OSes Also tweak the freeBSD testing a bit.
document unofficially supported OSes Also tweak the freeBSD testing a bit.
The LLVM verifier is the second slowest pass after LiveIRVariables (2.4%/2.085 s). It's unnecessary and rarely catches stuff that the assertions don't. We should only run it in debug rustc builds.
The text was updated successfully, but these errors were encountered: