This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Strange behaviour gcc 3.0

To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
Subject: Re: Strange behaviour gcc 3.0
From: Andreas Jaeger <aj at suse dot de>
Date: Wed, 01 Aug 2001 15:27:04 +0200
Cc: Igmar Palsenberg <i dot palsenberg at jdimedia dot nl>,Alexandre Oliva <aoliva at redhat dot com>, <gcc-bugs at gcc dot gnu dot org>,<gcc at gcc dot gnu dot org>
References: <Pine.LNX.4.33.0108011440220.28577-100000@jdi.jdimedia.nl><Pine.LNX.4.33.0108011440220.28577-100000@jdi.jdimedia.nl><5.1.0.14.2.20010801151903.04687e08@mail.lauterbach.com>

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,

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Follow-Ups:
- Re: Strange behaviour gcc 3.0
  - From: Franz Sirl

References:
- Re: Strange behaviour gcc 3.0
  - From: Igmar Palsenberg
- Re: Strange behaviour gcc 3.0
  - From: Franz Sirl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]