-
Notifications
You must be signed in to change notification settings - Fork 84
Description
But the other worrying point is that we're apparently printing something during solving itself. That's unusual, because usually it's just one solver stats printout after another. Perhaps there's some internal unnecessary string conversion taking place as well.
The analyses should not be using
Pretty
to convert things tostring
s during the analysis (unlesswarn_at
isearly
at least). I may be wrong, but I can't currently think of a legitimate reason to do that.
It might help to do an sv-benchmarks run with-v
to get the backtrace at that point. I think the backtrace should still contain the entire non-signal-handler stack, so it would expose where are we usingPretty
during analysis.Of course avoiding that isn't a particularly reliable fix, but it would make sense to avoid it anyway for performance reasons.