the order in which function arguments are put onto stack

[crs_zxf]

Promble solved! Thanks to salem!

I wrote the following code to test the order in which function arguments are put onto the stack, and I got wired result:

void print_char(char c1, char c2)
{
        printf("%p %p\n", &c1, &c2);
}

void print_float(float f1, float f2)
{
        printf("%p %p\n", &f1, &f2);
}

int main(int argc, char **argv)
{
        print_char('c', 'd');
        print_float(1.2, 2.3);

        return 0;
}

the result is:

0xbfcafef4 0xbfcafef0
0xbfcaff00 0xbfcaff04

which means for function print_char, the first argument is put onto the stack first, while for function print_float, the second argument is put first, why??

The code is run on 32-bit linux.

[Salem]

I get the same kind of result.

From looking at the assembler, chars are first copied to internal local variables, and what you see are pointers to those hidden locals, not pointers to the actual parameters.

[crs_zxf]

I get the same kind of result.

From looking at the assembler, chars are first copied to internal local variables, and what you see are pointers to those hidden locals, not pointers to the actual parameters.

You're right, thank you so much, you remind me of a very good way to solve this problem.