public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nbecker@fred.net
To: gcc-gnats@gcc.gnu.org
Cc: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Subject: c++/8640: template specialization bug #2 (gcc3.2)
Date: Mon, 25 Nov 2002 21:16:00 -0000	[thread overview]
Message-ID: <20021119154422.14261.qmail@sources.redhat.com> (raw)


>Number:         8640
>Category:       c++
>Synopsis:       template specialization bug #2 (gcc3.2)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 19 07:46:05 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     nbecker@fred.net
>Release:        3.2
>Organization:
>Environment:
linux
>Description:
THis should not give an error:

gcc -c -v bug.cc
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit
Thread model: posix
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
 /usr/lib/gcc-lib/i386-redhat-linux/3.2/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0 -D__GXX_ABI_VERSION=102 -D__ELF__ -Dunix -D__gnu_linux__ -Dlinux -D__ELF__ -D__unix__ -D__gnu_linux__ -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_i386__ bug.cc -D__GNUG__=3 -D__DEPRECATED -D__EXCEPTIONS -quiet -dumpbase bug.cc -version -o /tmp/cc5OJSQs.s
GNU CPP version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) (cpplib) (i386 Linux/ELF)
GNU C++ version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) (i386-redhat-linux)
	compiled by GNU C version 3.2 20020903 (Red Hat Linux 8.0 3.2-7).
ignoring nonexistent directory "/usr/i386-redhat-linux/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/include/c++/3.2
 /usr/include/c++/3.2/i386-redhat-linux
 /usr/include/c++/3.2/backward
 /usr/local/include
 /usr/lib/gcc-lib/i386-redhat-linux/3.2/include
 /usr/include
End of search list.
bug.cc: In function `int main()':
bug.cc:7: call of overloaded `foo(X<int>)' is ambiguous
bug.cc:3: candidates are: void foo(T) [with int shift = 1, T = X<int>]
bug.cc:4:                 void foo(X<T>) [with int shift = 1, T = int]
>How-To-Repeat:
compile
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="bug.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.cc"

dGVtcGxhdGUgPHR5cGVuYW1lIFQ+IGNsYXNzIFgge307Cgp0ZW1wbGF0ZTxpbnQgc2hpZnQsIHR5
cGVuYW1lIFQ+IHZvaWQgZm9vIChUIHgpIHsgZXJyb3I7IH0KdGVtcGxhdGU8aW50IHNoaWZ0LCB0
eXBlbmFtZSBUPiB2b2lkIGZvbyAoWDxUPiB4KSB7fQoKaW50IG1haW4gKCkgewogIGZvbzwxPiAo
WDxpbnQ+KCkpOwp9Cg==


             reply	other threads:[~2002-11-19 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 21:16 nbecker [this message]
2002-11-25 22:06 bangerth

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=20021119154422.14261.qmail@sources.redhat.com \
    --to=nbecker@fred.net \
    --cc=bangerth@ticam.utexas.edu \
    --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).