Strange behaviour gcc 3.0

[Franz Sirl]

At 15:27 01.08.2001, Andreas Jaeger wrote:
>Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
>
> >
> > BTW, why do we need this at all in the glibc sources? gcc-3.0 can
> > optimize printf the same way as fprintf, I don't see any advantages of
> > this #define...
>
>Feel free to send a patch for GCC to replace printf (...) with fprintf
>(stdout,...).  I expect that glibc will remove the macro in this case,

No, I'll send a patch to delete this #define in bits/stdio.h, unless you 
can explain me why it is advantageous to have it, because gcc-3.0 can 
optimize _both_ printf and fprintf.

Franz.