From: Jason Merrill <jason@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>, egcs@cygnus.com
Subject: Re: (1.0.2) std/bastring.h change -- Why add std/bastring.cc?
Date: Tue, 17 Feb 1998 13:54:00 -0000 [thread overview]
Message-ID: <u967mem1o4.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199802171840.KAA06006.cygnus.egcs@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@synopsys.com> writes:
>> Both pre-1.0.2 and new'ish snapshots have the Jason's Feb 12 change
>> where he adds bastring.cc to bastring.h. Why was this necessary? It
>> would seem to cause unnecessary code-bloat on non-ELF (and PE when
>> the bugs are fixed) systems. What am I missing here?
This was motivated by the undefined symbols on linux problem; the library
was being built thread-safe, and user code not, and the two are not
link-compatible.
In general, the previous arrangement was restricting people from using any
instantiation of basic_string other than the usual one.
> It is bloat on ELF platforms too: bigger object files, and the string
> functions are no longer in the shared library.
Actually, they are.
I suppose we should resurrect sinst.h.
Jason
next prev parent reply other threads:[~1998-02-17 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-17 9:51 Mumit Khan
1998-02-17 10:40 ` Joe Buck
[not found] ` <199802171840.KAA06006.cygnus.egcs@atrus.synopsys.com>
1998-02-17 13:54 ` Jason Merrill [this message]
1998-02-17 15:16 ` H.J. Lu
1998-02-17 23:59 ` Mumit Khan
1998-02-18 14:54 ` A STL patch for egcs 1.0.2 H.J. Lu
1998-02-18 14:54 ` (1.0.2) std/bastring.h change -- Why add std/bastring.cc? H.J. Lu
[not found] ` <m0y5H2p-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:45 ` Jason Merrill
[not found] ` <m0y5H5T-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:47 ` A STL patch for egcs 1.0.2 Jason Merrill
1998-02-19 10:47 ` H.J. Lu
1998-02-19 12:42 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 12:26 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 11:09 ` Jason Merrill
1998-02-19 14:09 ` Ulrich Drepper
1998-02-22 16:39 ` Jeffrey A Law
1998-02-23 11:00 ` H.J. Lu
1998-02-23 9:19 ` 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=u967mem1o4.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.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).