Eero Tamminen wrote:
They catch there being no prototype (neither for the return values or arguments) which was what you complained about.
The problem discussed here is about functions returning doubles into fp0 instead of d0/d1. This never causes problems in the function *definition*. But it causes problems when the function is *used* if no prototype is given (register mismatch). Your warnings are useful to make clean function definitions and prototypes, but they don't warn about anything if the *caller* forgets to include the prototype.
I'm tired, I stop here.
True, it's not default for C, but if one uses GCC, one would be mad not to use the warning facilities it provides over things mandatated just by the standard.
Of course. -- Vincent Rivière