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-conv
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
Kai Tietz changed:
What|Removed |Added
Known to work|4.4.0, 4.5.0, 4.6.0, 4.7.0, |
|4.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
--- Comment #10 from Paolo Carlini 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.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
--- Comment #9 from Kai Tietz 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, std
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
--- Comment #8 from Paolo Carlini 2012-11-22
19:08:14 UTC ---
So it works everywhere? ;)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
Kai Tietz changed:
What|Removed |Added
Component|target |c++
Known to work|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
Ozkan Sezer changed:
What|Removed |Added
CC||sezeroz at gmail dot com
--- Comm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
--- Comment #1 from niXman 2012-10-10 19:53:48 UTC
---
used i686-w64-mingw32
