public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36834] structure return ABI for windows targets differs from native MSVC
Date: Sat, 18 Dec 2010 10:38:00 -0000 [thread overview]
Message-ID: <bug-36834-4-Cbzkt9yrYU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36834-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36834
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Known to fail| |
--- Comment #14 from Kai Tietz <ktietz at gcc dot gnu.org> 2010-12-18 10:38:11 UTC ---
By this new attribute functions can be explicit marked to use VC compatible
aggregate return pointer handling.
I don't plan to backmerge this fix to 4.5.x tree, so I close this bug as fixed
for 4.6 tree. For 4.7 there is planned to introduce for mingw 32-bit target the
callabi MS_ABI/SYSV_ABI (as it is already present for 64-bit mingw target).
This will then automatically switch on MS specific calling convention changes -
eg ms-bitfield, caller-pops-aggregate-return, and co.
next prev parent reply other threads:[~2010-12-18 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-36834-4@http.gcc.gnu.org/bugzilla/>
2010-12-18 10:16 ` ktietz at gcc dot gnu.org
2010-12-18 10:38 ` ktietz at gcc dot gnu.org [this message]
2014-02-16 13:13 ` jackie.rosen at hushmail dot com
2008-07-15 9:28 [Bug target/36834] New: structure return ABI for windows targets differs from nbative MSVC 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-4-Cbzkt9yrYU@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).