From: David Edelsohn <dje@watson.ibm.com>
To: Richard Henderson <rth@cygnus.com>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Zack Weinberg <zack@rabi.columbia.edu>,
meissner@cygnus.com, linuxppc-dev@lists.linuxppc.org,
egcs-patches@egcs.cygnus.com
Subject: Re: PATCH: Fix 2 PPC/SYSV varargs problems
Date: Thu, 29 Apr 1999 23:08:18 -0400 [thread overview]
Message-ID: <9904300308.AA40106@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Richard Henderson <rth@cygnus.com> of "Thu, 29 Apr 1999 20:02:22 PDT." <19990429200222.B27844@cygnus.com>
>>>>> Richard Henderson writes:
Richard> It certainly isn't invasive; as for kludginess, it's in good company
Richard> with the way the alpha port has done things for a long time. Infer
Richard> what you will with that. ;-)
I am much more comfortable with a patch along the lines of
Richard's proposal -- both in the short term for egcs-1.2 release and as a
long-term solution. I do not think that there is an elegant way to fix
this.
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. ]]
next prev parent reply other threads:[~1999-04-30 3:08 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 [this message]
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
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=9904300308.AA40106@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=egcs-patches@egcs.cygnus.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=meissner@cygnus.com \
--cc=rth@cygnus.com \
--cc=zack@rabi.columbia.edu \
/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.