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++/26571] [4.0/4.1/4.2 regression] Bad diagnostic using type modifier with struct
Date: Wed, 06 Sep 2006 05:28:00 -0000	[thread overview]
Message-ID: <20060906052816.6194.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26571-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jason at gcc dot gnu dot org  2006-09-06 05:28 -------
Subject: Bug 26571

Author: jason
Date: Wed Sep  6 05:28:08 2006
New Revision: 116715

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116715
Log:
        PR c++/26571
        * parser.c (cp_parser_diagnose_invalid_type_name): Handle the case
        where the name is a type used incorrectly.

Added:
    trunk/gcc/testsuite/g++.dg/parse/typespec1.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26571


  parent reply	other threads:[~2006-09-06  5:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  2:56 [Bug c++/26571] New: " reichelt at gcc dot gnu dot org
2006-03-06 13:05 ` [Bug c++/26571] " pinskia at gcc dot gnu dot org
2006-03-11  3:22 ` mmitchel at gcc dot gnu dot org
2006-06-04 18:00 ` mmitchel at gcc dot gnu dot org
2006-09-06  0:12 ` jason at gcc dot gnu dot org
2006-09-06  5:28 ` jason at gcc dot gnu dot org [this message]
2006-09-07 22:27 ` [Bug c++/26571] [4.0/4.1 " jason at gcc dot gnu dot org
2006-09-07 22:38 ` jason at gcc dot gnu dot org
2006-09-07 23:04 ` jason at gcc dot gnu dot org
2006-09-07 23:07 ` jason 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=20060906052816.6194.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: 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).