public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/28513] [4.2/4.3/4.4 Regression] QOI: Diagnostic missing since 3.3.x when naming rule is violated Date: Thu, 20 Nov 2008 20:26:00 -0000 [thread overview] Message-ID: <20081120202459.14914.qmail@sourceware.org> (raw) In-Reply-To: <bug-28513-7852@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from jason at gcc dot gnu dot org 2008-11-20 20:24 ------- Subject: Bug 28513 Author: jason Date: Thu Nov 20 20:23:32 2008 New Revision: 142056 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142056 Log: PR c++/28513 * parser.c (cp_parser_class_name): Call maybe_note_name_used_in_class. Added: trunk/gcc/testsuite/g++.dg/lookup/name-clash7.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/parser.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28513
next prev parent reply other threads:[~2008-11-20 20:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-27 16:45 [Bug c++/28513] New: " rleigh at debian dot org 2006-07-29 5:24 ` [Bug c++/28513] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-07-31 23:37 ` mmitchel at gcc dot gnu dot org 2006-09-05 23:15 ` jason at gcc dot gnu dot org 2007-02-03 18:10 ` [Bug c++/28513] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-02-03 18:35 ` gdr at gcc dot gnu dot org 2007-02-03 20:42 ` pinskia at gcc dot gnu dot org 2007-02-14 9:32 ` mmitchel at gcc dot gnu dot org 2007-12-17 15:03 ` manu at gcc dot gnu dot org 2008-07-04 21:27 ` [Bug c++/28513] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-11-03 10:45 ` manu at gcc dot gnu dot org 2008-11-20 19:35 ` jason at gcc dot gnu dot org 2008-11-20 20:26 ` jason at gcc dot gnu dot org [this message] 2008-11-20 20:28 ` jason at gcc dot gnu dot org 2009-04-29 15:21 ` pinskia at gcc dot gnu dot org
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=20081120202459.14914.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).