This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490
- From: ljrittle at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, molivier at users dot sourceforge dot net, nobody at gcc dot gnu dot org
- Date: 28 Jan 2002 20:57:22 -0000
- Subject: Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490
- Reply-to: ljrittle at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, molivier at users dot sourceforge dot net, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
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 <rehsack@web.de>
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