From: Jason Kim <jwk2@eecs.lehigh.edu>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
"linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: patch for problem with va-ppc.h included with egcs and gcc-2.95.2
Date: Tue, 30 Nov 1999 13:05:55 -0500 [thread overview]
Message-ID: <38441203.7183CD88@eecs.lehigh.edu> (raw)
In-Reply-To: 4.2.2.19991130110534.00b563b0@mail.lauterbach.com
> 1. this behaviour is mandated by the ABI
Hmm. I just checked the SYSVR4 ABI, and indeed it lists va_list as a typedef of
1 element array. Oh well. But I notice that va-ppc.h does not define
void *__va_arg(va_list argp, _va_arg_list_type type) which is *required* by the
same ABI <grin>
Do I smell a bug ?? ;)
> 2. it nicely spots a common programming error
Yes, but only in one assignment direction. In any case, it caught the error on
ssh, and I'll post LinuxPPC specific patches to ssh-2.0.13 soonish.
-jason
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-30 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 6:00 patch for problem with va-ppc.h included with egcs and gcc-2.95.2 Jason Kim
1999-11-30 10:58 ` Franz Sirl
1999-11-30 18:05 ` Jason Kim [this message]
1999-11-30 23:28 ` Jason Kim
1999-12-01 15:33 ` Franz Sirl
1999-12-01 19:18 ` Jason Kim
1999-12-01 19:41 ` Kevin Hendricks
1999-12-02 5:20 ` Jason Kim
1999-12-02 7:15 ` Richard Henderson
1999-12-02 7:27 ` Kevin Buettner
1999-12-02 16:15 ` Jason Kim
1999-12-01 19:43 ` David A. Gatwood
1999-12-02 2:04 ` Jason Kim
-- strict thread matches above, loose matches on Subject: below --
1999-11-29 21:03 Jason Kim
1999-11-29 22:45 ` Franz Sirl
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=38441203.7183CD88@eecs.lehigh.edu \
--to=jwk2@eecs.lehigh.edu \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc-patches@gcc.gnu.org \
--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).