public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	molivier@users.sourceforge.net, nobody@gcc.gnu.org
Subject: Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490
Date: Mon, 28 Jan 2002 12:57:00 -0000	[thread overview]
Message-ID: <20020128205722.11392.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-01-28 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 12:57 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-11 13:46 Phil Edwards
2001-07-09  1:56 Mathieu Olivier
2001-07-06 12:16 Phil Edwards
2001-07-05 14:36 Phil Edwards
2001-07-05 14:06 Phil Edwards
2001-07-04  8:56 molivier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020128205722.11392.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=molivier@users.sourceforge.net \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).