This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
- To: wilson at cygnus dot com (Jim Wilson)
- Subject: Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
- From: "Philippe De Muyter" <phdm at macqel dot be>
- Date: Fri, 17 Apr 1998 10:43:20 +0200 (MET DST)
- Cc: ghazi at caip dot rutgers dot edu, bothner at cygnus dot com, egcs at cygnus dot com, law at cygnus dot com
> In any case, it doesn't really matter. We don't need to define
> __USE_FIXED_PROTOTYPES__. It is true that some systems will be missing
> a malloc prototype, but we only need a prototype if char * and int are
> different sizes, and we can be sure that all of those systems do have
> a malloc prototype already.
We also need a prototype if the return convention for pointers and ints
are different (e.g. on some m68k systems : d0 for ints a0 for pointers)
Another reason for needing a prototype is when we take the address
of the function.