public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alvinhochun at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64384] mingw-w64: stdcall function returning an aggregate is incompatible with MS ABI Date: Wed, 28 Dec 2022 09:50:25 +0000 [thread overview] Message-ID: <bug-64384-4-NVJfQPMGsM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64384-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64384 Alvin Wong <alvinhochun at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alvinhochun at gmail dot com --- Comment #8 from Alvin Wong <alvinhochun at gmail dot com> --- According to https://devblogs.microsoft.com/oldnewthing/20220113-00/?p=106152, Microsoft acknowledged that the behaviour is different between free function and C++ member functions, and that it does cause breakage of the COM ABI between C and C++. What they have done is to update the MIDL compiler to generate C bindings compatible with the C++ ABI. (I filed https://bugs.winehq.org/show_bug.cgi?id=54226 for implementing the same function in widl.) In this sense, the current behaviour of gcc and g++ regarding free functions should be correct and does not need fixing. Only the ABI for C++ class member functions are wrong.
next prev parent reply other threads:[~2022-12-28 9:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-23 13:39 [Bug target/64384] New: " mity at morous dot org 2014-12-23 13:55 ` [Bug target/64384] " jacek at codeweavers dot com 2014-12-23 14:42 ` ktietz at gcc dot gnu.org 2014-12-30 23:09 ` daniel.c.klauer at web dot de 2014-12-30 23:45 ` mity at morous dot org 2014-12-31 16:25 ` daniel.c.klauer at web dot de 2020-06-15 2:20 ` mizvekov at gmail dot com 2022-12-28 9:50 ` alvinhochun at gmail dot com [this message] 2022-12-28 10:02 ` alvinhochun at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-64384-4-NVJfQPMGsM@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).