From: Jason Kim <jwk2@eecs.lehigh.edu>
To: khendricks@ivey.uwo.ca,
"linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"David A. Gatwood" <dgatwood@deepspace.mklinux.org>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Subject: Re: patch for problem with va-ppc.h included with egcs and gcc-2.95.2
Date: Thu, 02 Dec 1999 00:20:06 -0500 [thread overview]
Message-ID: <38460186.8CEC249C@eecs.lehigh.edu> (raw)
In-Reply-To: 99120114490800.04790@localhost.localdomain
Kevin Hendricks wrote:
> If there is any way to change this without beaking backward compatibility with
> pre-compiled shared libs and things, I would vote for it.
>
Well, xemacs-21.1.8, Mesa-3.0, gcc-2.95.2, xscreensaver-3.21, gle-2.3 and
ssh-2.0.13 all compile and link against the older dynamic libraries, but use the
va_list definition from my patch. All seem to work fine. They were all compiled
from gcc-2.95.2 and binutils-2.95.?? on an otheriwise standard LinuxPPC 1999 Q3
install on my Apple B&W G3.
It seems that the va_list is more or less isolated from the library interface
issues, as user code that I've seen don't ever pass back va_list to library
code, so having the patch seems to be safe, at least for above packages.
Anybody have any examples of where there IS va_list passage from user code to
existing dynlib code (or vice versa)? I tried a bit, and couldn't find any, and
am thinking that there isn't any. If that is the case, then applying the patch
en-mass
seems harmless way for getting rid of the array based va_list once and for all.
Feedback please.
thanks.
-jason.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-02 5:20 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
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 [this message]
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=38460186.8CEC249C@eecs.lehigh.edu \
--to=jwk2@eecs.lehigh.edu \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=dgatwood@deepspace.mklinux.org \
--cc=gcc-patches@gcc.gnu.org \
--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 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.