2010/3/4 Tor Lillqvist <[email protected]>:
>> Maybe, but exception handling still won't work.
>
> Isn't there other things also that are incompatible, like vtables and
> whatnot? Doesn't some FAQ say that different C++ compilers use
> different name mangling on purpose because even if they would use the
> same mangling, one could still not in general use C++ (classes/objects
> created by) code compiled by one compiler from code compiled by
> another compiler.
>
> --tml
I agree for specific calling conventions used for 32-bit. On 64-bit
the calling convention is the same for C and C++. Major issue are the
vbtables of VC. As long as just vtables are used, the layout can
shared and not much problems are to be expected here.
In general such a feature could be mainly used (and here it is indeed
pretty interesting) to be able to call global functions / symbols
exported in different mangle schema. The map isn't identical, but for
a lot of cases it is possible.
Maybe, if this feature would be available, there would be interest to
implement for 32-bit win32 in gcc the thiscall-calling convention,
which would then allow (as for 64-bit already) to share even simple
classes.
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
