From: Jeffrey A Law <law@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
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: <17405.881916507@hurl.cygnus.com> (raw)
In-Reply-To: <m0xgQVs-0004ecC@ocean.lucon.org>
In message < m0xgQVs-0004ecC@ocean.lucon.org >you write:
> > Or are you saying that a library called with the old version would be
> > entirely self contained and thus we don't have to worry about mixing?
> >
>
> Yes. One shared library will only call one of the old/new interfaces
> which is determined at the library build time by gcc.
OK. It sounds like this is the key point to remember. Any particular
library or main program will only call one of the two interfaces and
thus we don't have a mixing problem.
[ ... ]
> Please keep in mind, __EH_FRAME_BEGIN__ is a static variable local
> to each binary. Since we keep both interfaces, we are ok.
This was one of the key points I was missing. With your explaination
this aspect of the code makes much more sense.
I've got your patch intmy tree and I'll set up a build overnight.
I think we also need to install Paul Eggert's most recent change to
write_c_file_glob, then tweak it to use the new names.
jeff
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
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 [this message]
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=17405.881916507@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=hjl@lucon.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 read-only IMAP folder(s) and NNTP newsgroup(s).