egcs, does gcc fixincludes etc guarantee a stdlib.h exists?

[Jim Wilson]

	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)

Good point.  However, I think the same reasoning applies here.  Either these
systems must already have appropriate declarations in the system headers, or
else the compiler must already be using a safe ABI (e.g. some m68k systems
return pointers in both a0 and d0 just to be safe).  Otherwise, the compiler
that came with the system wouldn't work.

	Another reason for needing a prototype is when we take the address
	of the function.

Not clear what you mean.  A prototype is certainly desirable, but it is not
obvious that it is required.

If there is a problem, then we certainly should fix it, but I don't believe
that defining __USE_FIXED_PROTOTYPES__ is a good solution.

Jim