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


Petko Manolov <petkan at users dot sourceforge dot net> writes:

>> 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.

The ISO C standard defines printf and allows this behaviour for all
functions that are part of the standard.

>> 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?

Free-standing means basically you have no C Library and therefore gcc
will not do such optimizations,

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


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