Re: Problems with multithreading and slow compilation

[Hans Aberg]

At 01:41 +0200 2004/07/07, Laurence Finston wrote:
>I've been having a bit of trouble with the debugging output
>produced by Bison when `yydebug' is set to a non-zero value,
>when calling `yyparse()' multiple times in different threads.
>
>Since the output is just written to `stdout' (or maybe `stderr'),
>the output from the different invocations of `yyparse()' is all
>mixed up.
>
>I haven't examined the output closely enough to tell
>whether the actual calls to `printf()' (or whatever Bison uses)
>are interrupted, but I suspect they are.
>
>Would the Bison developers have any interest in implementing
>the following features?
>
>1) making it possible to redirect the debugging output to files,
>   one for each invocation of `yyparse()'.
>
>2) Protecting `stdout' and `stderr' with mutexes, to keep
>   writes to these streams from being interrupted
>   (unless they are already, of course).

It sounds as though it should be put onto the todo-list.

  Hans Aberg