From: hjl@lucon.org (H.J. Lu)
To: law@cygnus.com
Cc: gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: gcc 2.8.0 is broken on linux/x86 and more bug
Date: Fri, 12 Dec 1997 03:55:00 -0000 [thread overview]
Message-ID: <m0xgQ0h-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <17146.881913533@hurl.cygnus.com>
>
>
> In message < m0xgM3M-0004ecC@ocean.lucon.org >you write:
> > __register_frame () change in gcc 2.8.0 causes a big problem.
> > Since __register_frame () called in crtbegin.o is in libgcc2.c and
> > gcc -shared includes crtbegin.o and -lgcc, any libc.so built by
> > previous gcc has __register_frame () in libc.so. Now the ABI for
> > __register_frame () is changed, that is a big mess for Linux since
> > shared libraries are used a lot. When the ABI of a function in
> > shared library is changed like this, it doesn't work too well.
> It seems to me that we need two interfaces one with the old way one
> with the new way.
>
> Furthermore, we must avoid calling "free" on any of the objects which
> come from static storage instead of malloc. Thus, we have to keep track
> of which interface was used for each object so that we know whether or
> not its memory should be free'd.
>
> The compiler should always emit calls to the new interfaces; the old
> interfaces would be for existing copies of ld.so which use the old
> interfaces.
>
I think that is what my patch does. It keeps the old name and
appends _new to new interface. It seems to work for me.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1997-12-12 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9712112330.AA18404@vlsi1.ultra.nyu.edu>
1997-12-11 20:29 ` H.J. Lu
1997-12-11 23:56 ` Jeffrey A Law
1997-12-12 3:55 ` H.J. Lu [this message]
1997-12-12 0:18 ` Jeffrey A Law
1997-12-12 1:52 ` H.J. Lu
1997-12-12 3:55 ` Jeffrey A Law
1997-12-12 3:55 ` H.J. Lu
1997-12-12 3:55 ` Jeffrey A Law
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=m0xgQ0h-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=law@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).