public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18674] [3.4/4.0 Regression] G++ accepts bad elaborated type specifiers
Date: Thu, 25 Nov 2004 14:22:00 -0000	[thread overview]
Message-ID: <20041125142203.23413.qmail@sourceware.org> (raw)
In-Reply-To: <20041125141837.18674.valentin@lrde.epita.fr>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-25 14:22 -------
Confirmed:
: Search converges between 2003-08-12-trunk (#321) and 2003-08-13-trunk (#322).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |accepts-invalid
   Last reconfirmed|0000-00-00 00:00:00         |2004-11-25 14:22:01
               date|                            |
            Summary|G++ accepts bad elaborated  |[3.4/4.0 Regression] G++
                   |type specifiers             |accepts bad elaborated type
                   |                            |specifiers
   Target Milestone|---                         |3.4.4
            Version|0.0                         |4.0.0


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


  reply	other threads:[~2004-11-25 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 14:18 [Bug c++/18674] New: " gcc-bugzilla at gcc dot gnu dot org
2004-11-25 14:22 ` pinskia at gcc dot gnu dot org [this message]
2004-11-27  2:46 ` [Bug c++/18674] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-27 17:47 ` mmitchel at gcc dot gnu dot org
2004-11-29 20:11 ` cvs-commit at gcc dot gnu dot org
2004-11-29 20:23 ` [Bug c++/18674] [3.4 " mmitchel 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=20041125142203.23413.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).