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++/18368] [3.4/4.0 Regression] C++ error message regression Date: Mon, 08 Nov 2004 04:55:00 -0000 [thread overview] Message-ID: <20041108045539.20285.qmail@sourceware.org> (raw) In-Reply-To: <20041108044458.18368.sabre@nondot.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-08 04:55 ------- Confirmed, but the error message to me is clear (maybe I have read the error message too much). When I said there was most likely a dup, I was thinking of a related case, see PR 16189. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |diagnostic Last reconfirmed|0000-00-00 00:00:00 |2004-11-08 04:55:37 date| | Summary|C++ error message regression|[3.4/4.0 Regression] C++ | |error message regression Target Milestone|--- |3.4.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18368
next prev parent reply other threads:[~2004-11-08 4:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-08 4:45 [Bug c++/18368] New: " sabre at nondot dot org 2004-11-08 4:47 ` Daniel Berlin 2004-11-08 4:47 ` [Bug c++/18368] " dberlin at dberlin dot org 2004-11-08 4:55 ` pinskia at gcc dot gnu dot org [this message] 2004-11-27 17:12 ` [Bug c++/18368] [3.4/4.0 Regression] " 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++/18368] [3.4 " mmitchel at gcc dot gnu dot org 2005-05-19 17:24 ` mmitchel at gcc dot gnu dot org 2005-09-01 14:56 ` reichelt at gcc dot gnu dot org 2005-09-17 21:57 ` cvs-commit at gcc dot gnu dot org 2005-09-17 22:05 ` cvs-commit at gcc dot gnu dot org 2005-09-17 22:07 ` reichelt 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=20041108045539.20285.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).