[Piglit] [PATCH] util: call fflush() after printf() calls
brianp at vmware.com
Wed Jun 7 19:54:38 UTC 2017
On 06/07/2017 12:03 PM, Eric Anholt wrote:
> Brian Paul <brianp at vmware.com> writes:
>> Otherwise, on Windows, we don't see the printf() output until the program
>> exits. That's fine with the -auto option, but a problem w/out -auto.
> That's pretty broken.
Actually, I think it's allowed behavior.
> Could we just wrap printf/fprintf on windows to
> call down and then fflush(), instead of doing it in all the callers?
> You've hit the most commonly-called printf callers, but I don't want to
> have to do this in all the tests, too.
I think I can work around this with setvbuf() to disable buffering.
New patch coming.
More information about the Piglit