This is the mail archive of the gcc@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]
Other format:	[Raw text]

Re: printf optimiziation in gcc-3.2.x

From: Petko Manolov <petkan at users dot sourceforge dot net>
To: Andreas Jaeger <aj at suse dot de>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Mon, 10 Mar 2003 14:19:42 +0200 (EET)
Subject: Re: printf optimiziation in gcc-3.2.x
References: <Pine.LNX.4.50.0303101311280.389-100000@tequila.rakia.org><hoof4jigpy.fsf@byrd.suse.de>

> Use either of -fno-builtin-printf or -fno-builtin.

OK.  This seem to fix the problem, but while i can see why we builtin
functions like memcpy and strlen, i definitely can't in the case of
printf.  Or at least IMHO it shouldn't be the default behavior.

> Btw. if you have a free-standing environment, use -ffree-standing,

I don't know what free-standing environment is.  What i am using is an ARM
cross compiler and binutils on Linux.  What good is that environment?


thanks,
Petko

Follow-Ups:
- Re: printf optimiziation in gcc-3.2.x
  - From: Andreas Jaeger

References:
- printf optimiziation in gcc-3.2.x
  - From: Petko Manolov
- Re: printf optimiziation in gcc-3.2.x
  - From: Andreas Jaeger

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