From: David Edelsohn <dje@watson.ibm.com>
To: Richard Henderson <rth@cygnus.com>
Cc: law@cygnus.com, Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
egcs-patches@egcs.cygnus.com, meissner@cygnus.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: PATCH: Fix 2 PPC/SYSV varargs problems
Date: Wed, 12 May 1999 11:24:15 -0400 [thread overview]
Message-ID: <9905121524.AA32004@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Richard Henderson <rth@cygnus.com> of "Tue, 11 May 1999 23:48:42 PDT." <19990511234842.A26784@cygnus.com>
>>>>> Richard Henderson writes:
Richard> On Wed, May 12, 1999 at 12:19:53AM -0600, Jeffrey A Law wrote:
>> Has this problem been fixed? I see patch from Richard which looks like it
>> is related:
Richard> No, this is a different, though related, problem. I need to sit
Richard> down with the ABI to properly evaluate the patch. PPC SVR4 varargs
Richard> seems needlessly complex.
That is an understatement! PPC SVR4 varargs is a monstrosity that
attempted to pack the registers as tightly as possible and created an
endless mess as a result.
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-05-12 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-30 0:09 PATCH: Fix 2 PPC/SYSV varargs problems Franz Sirl
1999-04-30 2:48 ` Richard Henderson
1999-04-30 2:55 ` Zack Weinberg
1999-04-30 3:02 ` Richard Henderson
1999-04-30 3:08 ` David Edelsohn
1999-04-30 4:49 ` Gary Thomas
1999-04-30 13:42 ` Franz Sirl
1999-04-30 22:08 ` Richard Henderson
1999-05-03 12:44 ` Franz Sirl
1999-05-12 6:19 ` Jeffrey A Law
1999-05-12 6:48 ` Richard Henderson
1999-05-12 10:21 ` Franz Sirl
1999-05-12 15:24 ` David Edelsohn [this message]
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=9905121524.AA32004@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=egcs-patches@egcs.cygnus.com \
--cc=law@cygnus.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=meissner@cygnus.com \
--cc=rth@cygnus.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.