public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bursig at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36274] Please improve usage of template libs.
Date: Tue, 20 May 2008 16:07:00 -0000 [thread overview]
Message-ID: <20080520160702.24689.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36274-16198@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from bursig at gmail dot com 2008-05-20 16:07 -------
(In reply to comment #1)
> -frepo is/was supposed to deal with this
>
As I know -frepo simple force -fno-implicit-templates which rip all template
instantion from all objects and produce additional special files which are
needed for new/additional pre-link compiler call which inject missing
implementation. I'm not expert here but I suppose that gcc will simple build it
even some of those symbols will be available during link.
Sun propose simpler methodology... compiler know during build phase (via
-instlib) what (and what not) templates instance will be available during link
and simple don't emit code for it. There is no special pre-link phase, no
special files only normal linking (and unknown symbols when you don't and
proper -llibs flags).
As I know Sun CC per-default add stl implementation library via -instlib which
reduce build time of know/"prebuild in lib" stl templates instantions.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36274
next prev parent reply other threads:[~2008-05-20 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 9:02 [Bug c++/36274] New: " bursig at gmail dot com
2008-05-20 12:42 ` [Bug c++/36274] " rguenth at gcc dot gnu dot org
2008-05-20 13:11 ` pinskia at gcc dot gnu dot org
2008-05-20 16:07 ` bursig at gmail dot com [this message]
2008-05-20 16:22 ` bursig at gmail dot com
[not found] <bug-36274-4@http.gcc.gnu.org/bugzilla/>
2021-08-31 21:30 ` pinskia at gcc dot gnu.org
2021-09-01 8:23 ` redi at gcc dot gnu.org
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=20080520160702.24689.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).