On 06 Jun 2012, at 09:06, Eric Pouech wrote:
> that's a limitation of dwarf format (IIRC, from the specs, you have
> either the default CC for your programming language/ABI, or a specific
> one without defining it further)
Yes and no:
* the DWARF standard itself does not specify any calling conv
that's a limitation of dwarf format (IIRC, from the specs, you have
either the default CC for your programming language/ABI, or a specific
one without defining it further)
FYII, the codeview format reports correctly this information
note also that winedbg doesn't support calling functions in the
de
piler flag. I guess one more
research task for me :-)
Regards,
Roger
From: Eric Pouech
To: Roger Cruz
Cc: Wine Devel
Sent: Wednesday, June 6, 2012 8:12 AM
Subject: Re: Wine's support for reporting calling conventions
dwarf4 allows each compiler vendor
dwarf4 allows each compiler vendor to add its own range of CC values
in the DW_AT_calling_convention field. this means that the vendor must
create its own table for mapping each used CC to a given value.
from a wine standpoint, the list should be rather small (stdcall,
fastcall...) (on top of cdecl
Hi Eric,
Thanks for replying. I saw that in the DWARF spec and I was afraid that DWARF
may not provide detailed Info. But I also read in the spec that the compilers
use a DWARF extension feature to convey additional info such as calling
convention for each routine. Is there a way to coax GCC
In dlls/dbghelp/dwarf.c, there is this snippet of code which appears to
hard-code the calling convention to CALL_FAR_C. Does Wine not support
reporting a function's calling convention correctly then? Is it a limitation
of DWARF or just that it is not implemented? I can see that DWARF has a
