public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Brian T. N. Gunney" <gunney@tux75.llnl.gov>
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/8550: undefined reference to fill and fill_n
Date: Tue, 19 Nov 2002 18:03:00 -0000	[thread overview]
Message-ID: <200211121854.gACIs7N25567@tux75.llnl.gov> (raw)


>Number:         8550
>Category:       libstdc++
>Synopsis:       undefined reference to fill and fill_n
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 12 10:56:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Brian T. N. Gunney
>Release:        3.2
>Organization:
Lawrence Livermore National Lab
>Environment:
System: Linux tux75.llnl.gov 2.4.9-31smp #1 SMP Tue Feb 26 06:55:00 EST 2002 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.2/configure --prefix=/usr/apps/gcc/3.2
>Description:
	
The fill and fill_n functions are missing when compiled with -fno-implicit-template,
leading to an error at link time.

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

>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-11-12 18:56 UTC|newest]

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

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=200211121854.gACIs7N25567@tux75.llnl.gov \
    --to=gunney@tux75.llnl.gov \
    --cc=gcc-gnats@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).