From: "Albert F. Niessner" <Al.Niessner@jpl.nasa.gov>
To: list gcc <help-gcc@gnu.org>
Subject: has '-fno-implicit-templates' changed??
Date: Tue, 15 Jan 2002 15:20:00 -0000 [thread overview]
Message-ID: <1011136834.5466.21.camel@morte.jpl.nasa.gov> (raw)
I have a hundred or more .cc files peppered with templates where I build
libraries from various groups of these files and some executables which
link in the libraries. With gcc 2.91.66, 2.95, and 2.96, I compile all
of the code with -fno-implicit-templates and then link with no errors
through any of it. The code runs fine and has been doing so for 2 years
now.
I just recently upgraded to 3.0.3 and am in the process of updating the
code to compile, link, and run with the new compiler and stdc++
libraries. The code compiles and builds all the libraries without error
right down to the last .cc file which has the main(). If I compile this
.cc file with -fno-implicit-templates I get a bunch errors at link time
indicating missing information related to the template
std::basic_ostream<>. In fact, the error seems to spread itself back
through the system to .cc that were compiled into one of my libraries.
If I compile without the -fno-implicit-template directive, then the link
is successful and it runs as expected.
So, what has changed with -fno-implicit-templates?
I grepped the change logs that came with gcc 3.0.3 for
implicit-templates and found nothing.
Al Niessner
reply other threads:[~2002-01-15 23:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1011136834.5466.21.camel@morte.jpl.nasa.gov \
--to=al.niessner@jpl.nasa.gov \
--cc=help-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).