From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11425 invoked by alias); 28 Jan 2002 20:57:22 -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 11393 invoked by uid 61); 28 Jan 2002 20:57:22 -0000 Date: Mon, 28 Jan 2002 12:57:00 -0000 Message-ID: <20020128205722.11392.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, molivier@users.sourceforge.net, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, molivier@users.sourceforge.net, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490 X-SW-Source: 2002-01/txt/msg00990.txt.bz2 List-Id: Synopsis: declaration of '__fmt' shadows previous local in ostream.tcc:490 State-Changed-From-To: open->closed State-Changed-By: ljrittle State-Changed-When: Mon Jan 28 12:57:21 2002 State-Changed-Why: Problem was fixed on mainline at some point. Fixed on 3.0.X branch before 3.0.4 release with: 2002-01-28 Jens Rehsack libstdc++/3561 * include/bits/ostream.tcc (__pad_char): Support -Wshadow -Werror. Here was my final analysis of the PR: It appears that being marked as code within a system header does not affect template instantiation that is actually triggered outside the header. If this issue only arose when one was compiling libstdc++-v3 (as I first thought), then we could just say, "don't compile libstdc++-v3 with both flags" but this issue impacts building user code outside the library with strict warning flags. The problem had nothing to do with prefix configuration. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3561