public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/2863: gcc accepts invalid explicit specialization syntax
@ 2002-06-14  9:51 lerdsuwa
  0 siblings, 0 replies; 3+ messages in thread
From: lerdsuwa @ 2002-06-14  9:51 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, lerdsuwa, nobody, wolfgang.bangerth

Synopsis: gcc accepts invalid explicit specialization syntax

Responsible-Changed-From-To: unassigned->lerdsuwa
Responsible-Changed-By: lerdsuwa
Responsible-Changed-When: Fri Jun 14 09:06:50 2002
Responsible-Changed-Why:
    Patch in progress.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2863


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c++/2863: gcc accepts invalid explicit specialization syntax
@ 2002-07-17  7:27 lerdsuwa
  0 siblings, 0 replies; 3+ messages in thread
From: lerdsuwa @ 2002-07-17  7:27 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, lerdsuwa, wolfgang.bangerth

Synopsis: gcc accepts invalid explicit specialization syntax

State-Changed-From-To: analyzed->closed
State-Changed-By: lerdsuwa
State-Changed-When: Wed Jul 17 07:27:56 2002
State-Changed-Why:
    Fixed in the main trunk (future GCC 3.3).

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2863


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c++/2863: gcc accepts invalid explicit specialization syntax
@ 2001-05-18  1:46 wolfgang.bangerth
  0 siblings, 0 replies; 3+ messages in thread
From: wolfgang.bangerth @ 2001-05-18  1:46 UTC (permalink / raw)
  To: gcc-gnats

>Number:         2863
>Category:       c++
>Synopsis:       gcc accepts invalid explicit specialization syntax
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Fri May 18 01:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
gcc 2.95, gcc cvs of May 05
>Description:
As a follow-up to the last report, talking about explicit
instantiations: gcc also allows explicit specializations
with wrong arguments. This is somewhat more critical, as
the compiler thereby looses the ability to warn you about
the then necessarily unused arguments.
Regards
  Wolfgang
>How-To-Repeat:
-----/gcc-bugs> cat a.cc
struct X {
    template <int dim> void f(int=0);
};

template <> void X::f<1> () {};


-----/gcc-bugs> ~/Config/gcc-ss-sun/bin/gcc -W -Wall -ansi -c a.cc -o /dev/null
-----/gcc-bugs> ~/Config/gcc-ss-sun/bin/gcc -v                                 
Reading specs from /home/atlas2/wolf/Config/gcc-ss-sun/bin/../lib/gcc-lib/sparc-sun-solaris2.7/3.0/specs
Configured with: ../gcc/configure --prefix=/home/people/wolf/Config/gcc-ss-sun --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld
Thread model: posix
gcc version 3.0 20010514 (prerelease)
>Fix:

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-07-17 14:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-06-14  9:51 c++/2863: gcc accepts invalid explicit specialization syntax lerdsuwa
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17  7:27 lerdsuwa
2001-05-18  1:46 wolfgang.bangerth

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).