postprocessing should happen before verification

[bchurchill]

When using the --results option, the verification sometimes fails because of an unsupported instruction that should be preprocessed away first.

[stefanheule]

This is not the behavior of the verification at the very end (that's done even without --results). Shouldn't the two behave the same (either both postprocess before verification, or both do it after)?

[bchurchill]

Yeah, both should verify after postprocessing. My thought is that what
the user sees is what should be verified.

Berkeley

On 07/07/2016 09:14 AM, Stefan Heule wrote:

This is not the behavior of the verification at the very end (that's
done even without --results). Shouldn't the two behave the same
(either both postprocess before verification, or both do it after)?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#919 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAnG6VSeZ_vNNZQ4Py_vQvjjqDntJ_O1ks5qTSXngaJpZM4JGmmu.

[stefanheule]

Okay, can you change the other place, too, then? Reopening the ticket.

[bchurchill]

I should be able to do this on Monday.

On 07/08/2016 07:43 PM, Stefan Heule wrote:

Okay, can you change the other place, too, then? Reopening the ticket.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#919 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAnG6awaBNwHDeA8Cl0TjpQsZJDYAfP-ks5qTwrsgaJpZM4JGmmu.

[bchurchill]

I haven't yet done this, because while the fix is easy, it's a pain to find an example to test this on. It's not on anyone's critical path, but it should get done sometime.