[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [f-cpu] calling conventions

> E.g. open() is often declared as
> int open(const char *name, int mode, ...);
> (because it can take two or three arguments) but in fact it may be
> (and eventually is) implemented as
> int open(const char *name, int mode, int perms) {
> ...
> }
> These two declarations must be compatible, or else a lot of `legacy'
> C code will break.

Okay, now I do know why GCC always refuse to mix register and stack parameters,
because of the sacrosanctity of this ugly legacy.

Well, I must admit that I don't like this calling convention but regarding with
your last argument, more intelligent rules are things best forgotten. Sorry for
annoying you so much.

To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/