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 01:52:00 -0000 [thread overview]
Message-ID: <m0xgQDb-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <17185.881913926@hurl.cygnus.com>
> > 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.
> I don't believe it handles the "free" issue correctly, then again, I'm
> not real familiar with that code.
>
> Please explain to me how it works if both register_frame and
> register_frame_new are are called by one program.
>
How does register_frame/register_frame_new get called? They are
called by crtbegin.o/collect2. User doesn't use them directly.
Since they are under our control, we always call the right one.
My glibc.so calls register_frame. But the binaries generated by
new egcs and gcc 2.8.0 call register_frame_new. In my environment
register_frame/register_frame_new are mixed when libc.so is used.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1997-12-12 1:52 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
1997-12-12 0:18 ` Jeffrey A Law
1997-12-12 1:52 ` H.J. Lu [this message]
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=m0xgQDb-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).