[Bug c++/54895] the compiler treats '__cdecl' & '__stdcall' as the same.

[ktietz at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895

--- Comment #12 from Kai Tietz  ---
This bug got partially fixed for x86 (32-bit) by PR/44282.  For x64 we have the
issue that there is made no difference between different calling-conventions,
as all variants are treated as standard fastcall-convention under the hood.

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[ktietz at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



Kai Tietz ktietz at gcc dot gnu.org changed:



   What|Removed |Added



  Component|target  |c++

  Known to work||4.4.0, 4.5.0, 4.6.0, 4.7.0,

   ||4.8.0



--- Comment #7 from Kai Tietz ktietz at gcc dot gnu.org 2012-11-22 18:55:40 
UTC ---

it is actual not a target issue.  it is more a general c++ issue as

calling-convention (call-abi attributes) aren't part of signature.

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[paolo.carlini at oracle dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



--- Comment #8 from Paolo Carlini paolo.carlini at oracle dot com 2012-11-22 
19:08:14 UTC ---

So it works everywhere? ;)

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[ktietz at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



--- Comment #9 from Kai Tietz ktietz at gcc dot gnu.org 2012-11-22 19:11:12 
UTC ---

(In reply to comment #8)

 So it works everywhere? ;)



Well, it doesn't work for all targets providing different calling-conventions

for functions.  Eg functions with regparm, stdcall, etc

That the sample is architecture specific, doesn't make it there for target

specific, isn't it? ;)

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[paolo.carlini at oracle dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



--- Comment #10 from Paolo Carlini paolo.carlini at oracle dot com 2012-11-22 
19:14:03 UTC ---

I don't know, I'm still finding the Known to work field pretty weird, to be

honest.

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[ktietz at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



Kai Tietz ktietz at gcc dot gnu.org changed:



   What|Removed |Added



  Known to work|4.4.0, 4.5.0, 4.6.0, 4.7.0, |

   |4.8.0   |

  Known to fail||4.4.0, 4.5.0, 4.6.0, 4.7.0,

   ||4.8.0



--- Comment #11 from Kai Tietz ktietz at gcc dot gnu.org 2012-11-22 19:15:49 
UTC ---

heh, oh duhh :}

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[i.nixman at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



--- Comment #1 from niXman i.nixman at gmail dot com 2012-10-10 19:53:48 UTC 
---

used i686-w64-mingw32

[Bug c++/54895] the compiler treats '__cdecl' '__stdcall' as the same.

[sezeroz at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895



Ozkan Sezer sezeroz at gmail dot com changed:



   What|Removed |Added



 CC||sezeroz at gmail dot com



--- Comment #2 from Ozkan Sezer sezeroz at gmail dot com 2012-10-10 20:17:26 
UTC ---

FWIW, this is not specific to 4.7 and goes back to at least 4.4.