From: David Edelsohn <dje@watson.ibm.com>
To: khendricks@ivey.uwo.ca
Cc: Andy Johnson <andyj@mc.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Issue with small struct return values
Date: Sat, 20 Jan 2001 16:37:33 -0500 [thread overview]
Message-ID: <200101202137.QAA22694@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from "Kevin B. Hendricks" <khendricks@ivey.uwo.ca> of "Sat, 20 Jan 2001 09:43:02 EST." <01012009430200.23836@localhost>
>>>>> "Kevin B Hendricks" writes:
Kevin> Did anyone actually get back to you on this issue?
Geoff and I discussed the issue with Andy previously and we
suggested that he post a message to these lists.
Kevin> I think people knew about this inconsistency but did not push matters.
Kevin> AFAIK, the gcc toolchain for ppc has always ignored that part of the abi.
IBM wants GCC (and therefore PowerPC Linux) to follow the SVR4 ABI
as written. GCC should not be inventing new ABIs when perfectly good and
correct ABIs exist. The longer this is allowed to continue, the harder it
is to correct.
GCC 3.0 (whose major number implies breaking backward
compatibility) seems like a good opportunity to correct this mistake.
Kevin> For what it is worth, I have found out that the abis implemented by PPC BSD,
Kevin> MacOSX, IBM, and PPC Linux all differ in strange ways (even Mac OSX ABI is
Kevin> not identical to IBM's EABI on which it was based). So in the long run, I am
Kevin> not sure that this issue matters.
Neither IBM (AIX PowerOpen ABI?) nor MacOSX are based on the eABI.
Yes, they differ, but that is because they are different ABIs. The Mac
PowerPC ABI is based on the IBM PowerOpen ABI.
This issue does matter because this mistake harms PowerPC
performance on these systems, and because other commercial compilers
implement the ABI correctly which causes this GCC mistake to interfere
with interoperability.
David
===============================================================================
David Edelsohn T.J. Watson Research Center
dje@watson.ibm.com P.O. Box 218
+1 914 945 4364 (TL 862) Yorktown Heights, NY 10598
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-20 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 22:14 Issue with small struct return values Andy Johnson
2001-01-20 14:43 ` Kevin B. Hendricks
2001-01-20 21:37 ` David Edelsohn [this message]
2001-01-21 0:04 ` Kevin B. Hendricks
2001-01-21 0:16 ` Kevin B. Hendricks
2001-01-21 0:41 ` David Edelsohn
2001-01-21 1:52 ` Kevin B. Hendricks
2001-01-21 2:02 ` David Edelsohn
2001-01-21 2:19 ` Kevin B. Hendricks
2001-01-21 2:30 ` David Edelsohn
2001-01-21 2:44 ` Kevin B. Hendricks
2001-01-21 2:45 ` David Edelsohn
2001-01-21 2:54 ` Kevin B. Hendricks
2001-01-21 3:31 ` David Edelsohn
2001-01-21 0:44 ` Brad Parker
2001-01-21 0:58 ` David Edelsohn
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=200101202137.QAA22694@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=andyj@mc.com \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).