From: hjl@lucon.org (H.J. Lu)
To: jbuck@synopsys.com (Joe Buck)
Cc: law@cygnus.com, rittle@comm.mot.com, egcs@cygnus.com
Subject: Re: Implications of tighter integration of libg++
Date: Mon, 09 Feb 1998 14:46:00 -0000 [thread overview]
Message-ID: <m0y202m-0004eeC@ocean.lucon.org> (raw)
In-Reply-To: <199802091739.JAA10303@atrus.synopsys.com>
>
>
> > > It is desirable to place libraries compiled against and dependent upon
> > > a given version of g++, and their related header files, into the
> > > compiler's lib and include directory.
>
> Yes, but once we have complete standards conformance, we should get to the
> point where libstdc++ always has the exact same API, so this kind of
Did you mean ABI or API? With the old g++, API might be the same. But
ABI changed. I was talking about vtable and name mangling.
> dependency doesn't really exist. I think that the compiler-specific
> lib directory really makes sense only for static libraries, not shared
> libraries.
>
>
>
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-09 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-24 23:19 Loren J. Rittle
1997-11-25 6:52 ` Manfred.Hollstein
1998-02-09 2:22 ` Jeffrey A Law
1998-02-09 7:13 ` Martin von Loewis
1998-02-09 14:46 ` Joe Buck
1998-02-09 15:33 ` Martin von Loewis
1998-02-09 21:34 ` H.J. Lu
1998-02-09 21:34 ` Joe Buck
1998-02-10 0:53 ` John A. Tamplin
1998-02-10 10:30 ` Joe Buck
1998-02-09 11:54 ` Joe Buck
1998-02-09 14:46 ` H.J. Lu [this message]
[not found] ` <5837.887019874.cygnus.egcs@hurl.cygnus.com>
1998-02-09 11:31 ` Jason Merrill
1998-02-09 11:54 ` Jeffrey A Law
1998-02-09 11:54 ` Jason Merrill
1998-02-09 15:33 ` Fred Fish
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=m0y202m-0004eeC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
--cc=law@cygnus.com \
--cc=rittle@comm.mot.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).