public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36834]  New: structure return ABI for windows targets differs from nbative MSVC
Date: Tue, 15 Jul 2008 09:28:00 -0000	[thread overview]
Message-ID: <bug-36834-4066@http.gcc.gnu.org/bugzilla/> (raw)

Like i386-netware, the native MS Windows compiler assumes that the CALLER pops
the stack for the implicit arguments pointing to aggregate return value.  This
differs from the default i386 ABI which assumes the CALLEE pops the stack.

This is documented at http://www.angelcode.com/dev/callconv/callconv.html in
the section  on __cdecl calling convention.

The bug was reported to mingw users list by Magnus Christensson at:
http://www.nabble.com/Problem-returning-C-struct-from-MinGW-to-MSVC-td18444899.html
This report contains a testcase demostrating the problem.

Danny


-- 
           Summary: structure return ABI for windows targets differs from
                    nbative MSVC
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dannysmith at users dot sourceforge dot net
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32


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


             reply	other threads:[~2008-07-15  9:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  9:28 dannysmith at users dot sourceforge dot net [this message]
2008-07-15  9:30 ` [Bug target/36834] " dannysmith at users dot sourceforge dot net
2008-07-17  8:16 ` [Bug target/36834] structure return ABI for windows targets differs from native MSVC dannysmith at users dot sourceforge dot net
2008-07-18  9:44 ` mattias at virtutech dot se
2009-03-11 11:35 ` rogerpack2005 at gmail dot com
2009-03-11 12:43 ` mattias at virtutech dot se
2009-03-14 21:14 ` rogerpack2005 at gmail dot com
2009-03-20 17:17 ` mattias at virtutech dot se
2009-03-21  1:04 ` dannysmith at users dot sourceforge dot net
2009-03-21 16:46 ` mattias at virtutech dot se
2009-03-21 21:49 ` mattias at virtutech dot se
2009-03-23 22:10 ` dannysmith at users dot sourceforge dot net
2009-06-24 12:05 ` ktietz at gcc dot gnu dot org

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-36834-4066@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).