public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8550: undefined reference to fill and fill_n
Date: Tue, 19 Nov 2002 18:08:00 -0000	[thread overview]
Message-ID: <20021112193606.28666.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/8550; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Brian T. N. Gunney" <gunney@tux75.llnl.gov>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/8550: undefined reference to fill and fill_n
Date: 12 Nov 2002 20:36:13 +0100

 "Brian T. N. Gunney" <gunney@tux75.llnl.gov> writes:
 
 | >State:          open
 | >Class:          sw-bug
 
 This is user confusion.
 
 [...]
 
 | The fill and fill_n functions are missing when compiled with -fno-implicit-template,
 | leading to an error at link time.
 
 Which matches the documented behaviour.
 
 | 
 | This is similar to bug 8172, in which I reported a missing operator+ for strings.
 | >How-To-Repeat:
 | 	
 | Program text:
 | #include <algorithm>
 | using namespace std;
 | int main() {
 |   double x[10];
 |   fill_n( x, 10, 1.0 );
 |   fill( x, x+10, 2.0 );
 |   return 0;
 | }
 | 
 | Compile command:
 | g++ -fno-implicit-templates  nofill.cc
 
 The above tells g++ not to implicitly instantiate the required
 definitions.  Which means you *ought* to manually provide them --
 usually through explicit instantiation.  
 
 The simple way fo fix this is: don't do that.
 
 -- Gaby


             reply	other threads:[~2002-11-12 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 18:08 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 18:12 gdr
2002-11-19 18:04 paolo
2002-11-19 18:03 Brian T. N. Gunney

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=20021112193606.28666.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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).