public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.c.klauer at web dot de" <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: Tue, 30 Dec 2014 23:09:00 -0000	[thread overview]
Message-ID: <bug-64384-4-7rMEmRsMrM@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

daniel.c.klauer at web dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.c.klauer at web dot de

--- Comment #3 from daniel.c.klauer at web dot de ---
It seems there is a difference between gcc and ms with regards to return in
register for C++ methods (regardless of stdcall/cdecl/thiscall).

Tested with i686-w64-mingw32 gcc 4.9.2 and cl.exe from VS 2010:

struct A {
    int field1;
};

struct A getA(void) {
    struct A a = {123};
    return a;
}

C function: both gcc and ms return in register (struct is small enough), ok.

struct A {
    int field1;
};

class Test {
public:
    A getA();
};

A Test::getA() {
    struct A a = {123};
    return a;
}

C++ method: ms returns in temp var on stack (as for big structs), but gcc
returns in register. 

The same happens for struct containing two floats (as in the original crash
issue reported on mingw-w64 mailing list).

Maybe (on 32bit) ms never uses return in register for C++ methods with
aggregate result?


  parent reply	other threads:[~2014-12-30 23:09 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 [this message]
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-7rMEmRsMrM@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).