From: Zack Weinberg <zack@rabi.columbia.edu>
To: Richard Henderson <rth@cygnus.com>
Cc: meissner@cygnus.com, David Edelsohn <dje@watson.ibm.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: PATCH: Fix 2 PPC/SYSV varargs problems
Date: Thu, 29 Apr 1999 22:55:36 -0400 [thread overview]
Message-ID: <199904300255.WAA16851@blastula.phys.columbia.edu> (raw)
In-Reply-To: Your message of "Thu, 29 Apr 1999 19:48:17 PDT." <19990429194817.B20300@cygnus.com>
On Thu, 29 Apr 1999 19:48:17 -0700, Richard Henderson wrote:
>On Fri, Apr 30, 1999 at 02:09:09AM +0200, Franz Sirl wrote:
>> 1. the varargs save area calculation bug, this is a hack and Richard ;-)
>> probably won't like it, but maybe it's good enough for egcs-1.2
>
>You're right -- I hate it. You'll have made it so I can't build a
>ppc cross compiler on my Alphas, and you'll have killed the compiler
>for a ppc64-linux.
ObDumbQuestion: Is this a bug we really need to fix for 1.2? It's
been around for awhile and all the proposed solutions are either dirty
kludges or too invasive.
zw
[[ 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 2:55 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 [this message]
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
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=199904300255.WAA16851@blastula.phys.columbia.edu \
--to=zack@rabi.columbia.edu \
--cc=dje@watson.ibm.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 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).