Re: Some experiments with cpplib's output end

[Zack Weinberg <zack at codesourcery dot com>]

On Thu, Sep 27, 2001 at 07:44:02AM +0100, Neil Booth wrote:
> Zack Weinberg wrote:-
> 
> > We've squelched fputs_unlocked, but now cpp_output_token has to do
> > more work, which means we don't win as much as we might like.
> > Nonetheless this is definitely better than what we had.
> > 
> > It's possible to squeeze out another four seconds by using
> > fwrite_unlocked instead of fwrite, but this involves more autoconf
> > gook.  I am particularly unfond of it in this case, since the default
> > chosen by glibc is so completely and obviously wrong.
> 
> Thanks for the analysis, Zack.  I wonder if we're better something
> simple and braindead, like our own scratch buffer of size roughly 8K
> say, that we manage ourselves and only dump (probably bypassing stdio)
> when it's about to overflow?

I've been considering doing that for a long time - especially if it's
generic enough that we can use it for assembly output too.  To date,
I've always been too lazy.

zw