public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sebor@roguewave.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/3797: gcc 3.0 fails to emit explicit specialization of a template member
Date: Tue, 24 Jul 2001 11:36:00 -0000	[thread overview]
Message-ID: <20010724183436.1293.qmail@sourceware.cygnus.com> (raw)

>Number:         3797
>Category:       c++
>Synopsis:       gcc 3.0 fails to emit explicit specialization of a template member
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 24 11:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     sebor@roguewave.com
>Release:        gcc version 3.0
>Organization:
>Environment:

>Description:
Declaring the explicit specialization of the member of the
class template causes the compiler to 'forget' to emit the
out-of-line symbol for the explicit specialization defined
later.

$ cat t.cpp
template <class T>
struct S
{
    int foo () { return 0; }
};

template <>
int S<int>::foo ();

template <>
int S<int>::foo () { return 1; }
$ g++ -c -v t.cpp   
Reading specs from /usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs
Configured with: ../gcc-3.0/configure --prefix=/usr/local/gcc-3.0 --enable-shared
Thread model: single
gcc version 3.0
 /usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__ -D__tune_pentiumpro__ t.cpp -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase t.cpp -version -o /tmp/ccoYegSb.s
GNU CPP version 3.0 (cpplib) (i386 Linux/ELF)
GNU C++ version 3.0 (i686-pc-linux-gnu)
        compiled by GNU C version 2.95.2 19991024 (release).
ignoring nonexistent directory "/usr/local/gcc-3.0/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/gcc-3.0/include/g++-v3
 /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu
 /usr/local/gcc-3.0/include/g++-v3/backward
 /usr/local/gcc-3.0/include
 /usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/include
 /usr/include
End of search list.
 as --traditional-format -V -Qy -o t.o /tmp/ccoYegSb.s
GNU assembler version 2.9.1 (i386-redhat-linux), using BFD version 2.9.1.0.23
$ nm t.o
$
>How-To-Repeat:
template <class T>
struct S
{
    int foo () { return 0; }
};

template <>
int S<int>::foo ();

template <>
int S<int>::foo () { return 1; }
>Fix:
Omit the declaration of the specialization or the definition
of the member of the primary template (neither is acceptable
if the specialization is to exist in a portable library).
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-24 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 11:36 sebor [this message]
2002-05-26  8:25 lerdsuwa
2002-06-01  8:09 lerdsuwa
2002-07-17  7:27 lerdsuwa

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=20010724183436.1293.qmail@sourceware.cygnus.com \
    --to=sebor@roguewave.com \
    --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).