From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20853 invoked by alias); 16 May 2003 14:46:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 20811 invoked by uid 71); 16 May 2003 14:46:01 -0000 Date: Fri, 16 May 2003 14:46:00 -0000 Message-ID: <20030516144601.20807.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: c++/10816 Reply-To: Wolfgang Bangerth X-SW-Source: 2003-05/txt/msg01847.txt.bz2 List-Id: The following reply was made to PR c++/10816; it has been noted by GNATS. From: Wolfgang Bangerth To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/10816 Date: Fri, 16 May 2003 09:44:09 -0500 (CDT) It's hard to tell, since gcc3.2.3 doesn't print _any_ warning messages on the code. But I have never seen such a bug for pre-3.3, so I think it must be a regression. 3.4 shows the same behavior with today's header files, but prints only one warning. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/