public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mity at morous dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64384] New: mingw-w64: stdcall function returning an aggregate is incompatible with MS ABI
Date: Tue, 23 Dec 2014 13:39:00 -0000	[thread overview]
Message-ID: <bug-64384-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64384
           Summary: mingw-w64: stdcall function returning an aggregate is
                    incompatible with MS ABI
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mity at morous dot org

When using COM interface (i.e. calling stdcall function/method), aggregates are
returned through an implicit parameter after the this/interface pointer,
according to MS ABI. However it is not so when using gcc.

This issue manifests itself when e.g. calling ID2D1RenderTarget::GetSize() from
<d2d1.h> as discussed here:

https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/?style=threaded&viewmonth=201412&viewday=23


Wine team encountered the issue too, they seem to "solve" the issue on their
side by ugly hacks and changing prototypes of the relevant functions for now:

https://www.winehq.org/pipermail/wine-patches/2014-September/134351.html


             reply	other threads:[~2014-12-23 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 13:39 mity at morous dot org [this message]
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
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@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: link
Be 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).