From: Nathan Sidwell <nathan@codesourcery.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Kazu Hirata <kazu@codesourcery.com>,
gcc-patches@gcc.gnu.org, law@redhat.com, schwab@suse.de
Subject: Re: [patch] m68k: Fix binary compatibility problem with -mno-strict-align. (Take 2)
Date: Wed, 29 Aug 2007 17:14:00 -0000 [thread overview]
Message-ID: <46D5A4E1.7020409@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291740060.1817@scrub.home>
Roman Zippel wrote:
> I see.
> What concerns me here is that this produces incompatibilities for ColdFire
> code between Linux and other targets. It also makes the support for this
> in libffi interesting (e.g. if you ever want Java support for ColdFire).
Agreed. But unfortunately it is what it is. There's more to ABIs than just
whether structures are returned in memory. For instance, %d0 and %a0 are used
differently too wrt structure returning. And of course there are other ABI
considerations too.
> Since this is a special case I would seriously consider to ignore the
> alignment mode for this in m68k_return_in_memory. Since this is an ABI
> issue there probably should be an option to get the old behaviour.
I'm strongly in favour of not breaking existing ABIs.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
next prev parent reply other threads:[~2007-08-29 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 15:59 Kazu Hirata
2007-08-28 13:32 ` Andreas Schwab
2007-08-29 14:57 ` Roman Zippel
2007-08-29 15:26 ` Kazu Hirata
2007-08-29 16:11 ` Roman Zippel
2007-08-29 17:14 ` Nathan Sidwell [this message]
2007-08-29 18:19 ` Roman Zippel
2007-08-29 18:28 ` Nathan Sidwell
2007-08-29 16:53 ` Nathan Sidwell
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=46D5A4E1.7020409@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kazu@codesourcery.com \
--cc=law@redhat.com \
--cc=schwab@suse.de \
--cc=zippel@linux-m68k.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).