public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/28080] header dependencies
Date: Fri, 23 Jun 2006 16:40:00 -0000 [thread overview]
Message-ID: <20060623163541.5471.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28080-8082@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from gdr at integrable-solutions dot net 2006-06-23 16:35 -------
Subject: Re: header dependencies
"chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> writes:
| I did implement a version of this myself, basically by writing a
| mapper around each container that did a few static_casts and mapped
| the functions to a void* version of the container. However, having a
| whole new bunch of inline functions causes problems for the
| compiler, without providing (as far as I could measure)
| significant reductions in the size of the executable.
I'm not surprised. We should be very cautious about increasing
abstraction penablty for the benefit of marginal reduction on header
dependencies. Runtime performance of the library should not be
under-emphasized.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28080
next prev parent reply other threads:[~2006-06-23 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:50 [Bug libstdc++/28080] New: " Woebbeking at web dot de
2006-06-19 10:15 ` [Bug libstdc++/28080] " pcarlini at suse dot de
2006-06-19 16:57 ` pinskia at gcc dot gnu dot org
2006-06-19 17:07 ` pinskia at gcc dot gnu dot org
2006-06-19 18:05 ` Woebbeking at web dot de
2006-06-19 18:11 ` pcarlini at suse dot de
2006-06-23 5:00 ` pinskia at gcc dot gnu dot org
2006-06-23 15:40 ` chris at bubblescope dot net
2006-06-23 16:40 ` gdr at integrable-solutions dot net [this message]
2006-06-23 17:03 ` chris at bubblescope dot net
2007-02-17 17:34 ` pcarlini at suse dot de
2007-02-17 20:42 ` Woebbeking at web dot de
2007-02-18 11:33 ` paolo at gcc dot gnu dot org
2007-02-20 18:16 ` bkoz at gcc dot gnu dot org
2007-02-20 21:23 ` paolo at gcc dot gnu dot org
2007-02-24 10:15 ` pcarlini at suse dot de
2007-02-26 9:37 ` paolo at gcc dot gnu dot org
2007-02-27 17:48 ` paolo at gcc dot gnu dot org
2007-03-02 16:22 ` paolo at gcc dot gnu dot org
2007-03-03 10:29 ` paolo at gcc dot gnu dot org
2007-03-04 0:20 ` paolo at gcc dot gnu dot org
2007-03-04 0:23 ` paolo at gcc dot gnu dot org
2007-03-06 17:43 ` paolo at gcc dot gnu dot org
2007-03-07 22:59 ` paolo at gcc dot gnu dot org
2007-03-10 20:30 ` paolo at gcc dot gnu dot org
2007-03-11 12:04 ` paolo at gcc dot gnu dot org
2007-03-11 12:07 ` pcarlini at suse dot de
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=20060623163541.5471.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).