[Bug c++/32505] Partial specialization halfway accepted after instantiation

2010-07-16 Thread jason at gcc dot gnu dot org
--- Comment #5 from jason at gcc dot gnu dot org 2010-07-17 04:13 --- Fixed for 4.6. -- jason at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIG

[Bug c++/32505] Partial specialization halfway accepted after instantiation

2010-07-16 Thread jason at gcc dot gnu dot org
--- Comment #4 from jason at gcc dot gnu dot org 2010-07-16 21:05 --- Subject: Bug 32505 Author: jason Date: Fri Jul 16 21:05:16 2010 New Revision: 162269 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162269 Log: PR c++/32505 * pt.c (process_partial_specializati

[Bug c++/32505] Partial specialization halfway accepted after instantiation

2010-07-16 Thread jason at gcc dot gnu dot org
-- jason at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jason at gcc dot gnu dot org |dot org

[Bug c++/32505] Partial specialization halfway accepted after instantiation

2010-07-16 Thread jason at gcc dot gnu dot org
--- Comment #3 from jason at gcc dot gnu dot org 2010-07-16 16:22 --- Confirmed; no diagnostic is required by the standard, but we really ought to give one anyway. Simpler testcase: template struct A { }; A a; template struct A { }; // { dg-error "A" } -- jason at gcc dot gnu dot

[Bug c++/32505] Partial specialization halfway accepted after instantiation

2009-12-08 Thread redi at gcc dot gnu dot org
--- Comment #2 from redi at gcc dot gnu dot org 2009-12-08 23:54 --- [temp.class.spec]/1 "A partial specialization shall be declared before the first use of a class template specialization that would make use of the partial specialization as the result of an implicit or explicit instantia

[Bug c++/32505] Partial specialization halfway accepted after instantiation

2007-06-25 Thread dascandy at gmail dot com
--- Comment #1 from dascandy at gmail dot com 2007-06-25 20:51 --- The problem doesn't produce a warning when compiled with -Wall -Wextra -pedantic. One of these (I expect -Wall is the best fit) should produce a warning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32505