Hello John,
Tuesday, July 7, 2009, 5:48:10 AM, you wrote:
you mean that on windows gcc, msvc and all other C compilers use the
same ABI for passing and packing structs?
Yes. If you think about it, otherwise it would be impossible to
interface with system provided shared libraries (like
On Tue, 2009-06-30 at 18:59 -0700, John Meacham wrote:
On Tue, Jun 30, 2009 at 01:18:32AM +0100, Duncan Coutts wrote:
On IA32 structs/unions passed as parameters go by value on the stack.
For structs/unions as function results, they are stored into a
caller-allocated area on the stack,
On Tue, Jun 30, 2009 at 01:18:32AM +0100, Duncan Coutts wrote:
On IA32 structs/unions passed as parameters go by value on the stack.
For structs/unions as function results, they are stored into a
caller-allocated area on the stack, pointed to by a hidden first arg.
It's different on each
Hello Duncan,
Tuesday, June 30, 2009, 12:03:15 AM, you wrote:
struct ex {
int x;
int y;
int z;
};
ex example_functions (ex p)
afaik, there is C ABI, that defines how to pass and return parameters
of simple types, it's common for all compilers supporting so-called
cdecl on
On Tue, 2009-06-30 at 00:45 +0400, Bulat Ziganshin wrote:
Hello Duncan,
Tuesday, June 30, 2009, 12:03:15 AM, you wrote:
struct ex {
int x;
int y;
int z;
};
ex example_functions (ex p)
afaik, there is C ABI, that defines how to pass and return parameters
of
