From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-173605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5851 invoked by alias); 19 Jan 2006 11:11:54 -0000
Received: (qmail 5842 invoked by uid 48); 19 Jan 2006 11:11:53 -0000
Date: Thu, 19 Jan 2006 11:11:00 -0000
Subject: [Bug c++/25855]  New: template specialisation not always found
X-Bugzilla-Reason: CC
Message-ID: <bug-25855-3563@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "mueller at kde dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2006-01/txt/msg01912.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

there seems to be a possibly a regression in c++ 4.0.2 / 4.1 and newer
depending on if BREAK and WORKAROUND is not defined in the attached testcase. 

I'm not 100% sure if this is defined behavior or not, or if the WORKAROUND is
actually the correct solution. So it varies between wrong-code, accepts-invalid
and invalid testcase. Input needed.


-- 
           Summary: template specialisation not always found
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mueller at kde dot org
  GCC host triplet: i686-unknown-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25855