[Ffmpeg-devel] stdint.h and inttypes.h for non-C99 compilers
Sat Dec 16 02:57:19 CET 2006
Christian Iversen <chrivers at iversen-net.dk> writes:
> On Friday 15 December 2006 13:50, M?ns Rullg?rd wrote:
>> Christian Iversen said:
>> > The stack is callee-cleared, and thus "register" is very much like
>> > (perhaps identical to) Borland C++'s "__fastcall" modifier:
>> Requiring the callee to restore the stack is simply stupid, IMHO.
> Well, that depends on the circumstance.
Give an example where the callee restoring the stack would be better.
>> Imagine what would happen if a function like printf were called with too
>> many arguments.
> What do you mean by "too many"?
int foo, bar;
printf("%d\n", foo, bar);
> Pascal calling convention is not used with the same style of varargs
> as cdecl, so the function will always know how many parameters it
> has accepted. This is never a problem in practice.
How is the number of arguments passed to the function? Whatever the
mechanism, it seems like a waste to me.
> Of course, calling conventions on x86 is a mess anyway. Now, the x86_64
> calling convention, that's something sane :-)
mru at inprovide.com
More information about the ffmpeg-devel