From: hjl@lucon.org (H.J. Lu)
To: egcs@tantalophile.demon.co.uk (Jamie Lokier)
Cc: law@upchuck.cygnus.com, egcs@egcs.cygnus.com
Subject: Re: __register_frame_info & shared library compatibility
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <m10VKyt-000ErMC@ocean.lucon.org> (raw)
Message-ID: <19990430231500.5Aioq-b-Vvinlt0rhCUvDze42YeZO_5uIt8KCDdDIUY@z> (raw)
In-Reply-To: <19990408215451.B21750@pcep-jamie.cern.ch>
>
> Is is possible to include a stub weak *definition* of
> __register_frame_info in crtbeginS.o, which is nothing more than a
> return instruction?
>
> Would that solve these temporary binary compatibility problems, without
> the permanent bloat?
>
That means we have to do more testing without much benefit. I don't
think it is wise for egcs people to spend any more time on this. It is
a glibc problem and let glibc people deal with it. If some glibc users
won't listen to the glibc people, they get what they deserved.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-07 5:14 Mark Kettenis
1999-04-07 5:33 ` Jeffrey A Law
1999-04-07 18:11 ` John Polstra
1999-04-07 23:36 ` Jeffrey A Law
1999-04-08 9:57 ` Jamie Lokier
1999-04-08 10:31 ` H.J. Lu
1999-04-08 12:44 ` Jeffrey A Law
1999-04-08 12:49 ` Jamie Lokier
1999-04-08 12:57 ` H.J. Lu
1999-04-08 13:12 ` Jeffrey A Law
1999-04-08 13:24 ` Jamie Lokier
1999-04-08 13:31 ` Jeffrey A Law
1999-04-08 13:42 ` Jamie Lokier
1999-04-08 13:54 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Jamie Lokier
1999-04-30 23:15 ` Jeffrey A Law
1999-04-08 14:38 ` Eric Kidd
1999-04-30 23:15 ` Eric Kidd
1999-04-30 23:15 ` Jamie Lokier
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-08 13:02 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Jamie Lokier
1999-04-08 12:55 ` Jamie Lokier
1999-04-08 13:01 ` H.J. Lu [this message]
1999-04-08 13:25 ` Jeffrey A Law
1999-04-08 13:33 ` Jamie Lokier
1999-04-08 13:47 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Jamie Lokier
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-08 13:05 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Jamie Lokier
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-08 12:28 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-21 11:53 ` David O'Brien
1999-04-21 12:00 ` Jamie Lokier
1999-04-21 13:02 ` David O'Brien
1999-04-21 13:20 ` Joe Buck
1999-04-21 13:33 ` Marc Espie
1999-04-22 22:29 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Marc Espie
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` David O'Brien
1999-04-30 23:15 ` Jamie Lokier
1999-04-21 12:41 ` "all the world's not Linux" Joe Buck
1999-04-21 12:59 ` David O'Brien
1999-04-21 13:04 ` David Edelsohn
1999-04-30 23:15 ` David Edelsohn
1999-04-30 23:15 ` David O'Brien
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` __register_frame_info & shared library compatibility David O'Brien
1999-04-30 23:15 ` Jamie Lokier
1999-04-08 14:56 ` John Polstra
1999-04-08 15:58 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-09 13:01 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-04-30 23:15 ` John Polstra
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` John Polstra
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
1999-04-21 19:14 N8TM
1999-04-30 23:15 ` N8TM
1999-04-14 5:58 Mark Kettenis
1999-04-14 14:15 ` Jeffrey A Law
1999-04-14 14:57 ` Mark Kettenis
1999-04-30 23:15 ` Mark Kettenis
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Mark Kettenis
1999-04-09 4:49 Mark Kettenis
1999-04-10 1:41 ` Jeffrey A Law
1999-04-10 6:41 ` Zack Weinberg
1999-04-11 21:21 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Zack Weinberg
1999-04-10 8:28 ` Mark Kettenis
1999-04-11 21:25 ` Jeffrey A Law
1999-04-12 6:15 ` Zack Weinberg
1999-04-13 21:05 ` Jeffrey A Law
1999-04-13 23:16 ` Zack Weinberg
1999-04-13 23:38 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Mark Kettenis
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Mark Kettenis
1999-04-06 14:00 Eric Kidd
1999-04-06 14:16 ` Zack Weinberg
1999-04-06 14:52 ` Eric Kidd
1999-04-06 15:16 ` Zack Weinberg
1999-04-06 15:39 ` Eric Kidd
1999-04-06 15:51 ` Zack Weinberg
1999-04-06 16:14 ` Eric Kidd
1999-04-30 23:15 ` Eric Kidd
1999-04-07 1:35 ` Andreas Schwab
1999-04-07 6:32 ` Zack Weinberg
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Andreas Schwab
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Eric Kidd
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Eric Kidd
1999-04-06 16:58 ` Jeffrey A Law
1999-04-06 17:35 ` Zack Weinberg
1999-04-06 17:55 ` H.J. Lu
1999-04-30 23:15 ` H.J. Lu
1999-04-07 2:10 ` Jeffrey A Law
1999-04-07 6:29 ` Zack Weinberg
1999-04-07 6:53 ` alex.buell
1999-04-30 23:15 ` alex.buell
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Zack Weinberg
1999-04-06 17:04 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Eric Kidd
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=m10VKyt-000ErMC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@egcs.cygnus.com \
--cc=egcs@tantalophile.demon.co.uk \
--cc=law@upchuck.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 read-only IMAP folder(s) and NNTP newsgroup(s).