public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13927] [3.4/3.5 Regression] duplicated error message on bad redeclaration of anon union
Date: Fri, 20 Feb 2004 08:57:00 -0000 [thread overview]
Message-ID: <20040220085743.5861.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040130062339.13927.mec.gnu@mindspring.com>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-02-20 08:57 -------
Subject: Bug 13927
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: mmitchel@gcc.gnu.org 2004-02-20 08:57:33
Modified files:
gcc/cp : ChangeLog decl.c name-lookup.c pt.c semantics.c
gcc/testsuite : ChangeLog
gcc/testsuite/g++.dg/other: error8.C
Added files:
gcc/testsuite/g++.dg/ext: packed5.C
gcc/testsuite/g++.dg/warn: Wunused-5.C
Log message:
PR c++/14199
* pt.c (tsubst_copy): Call mark_used for a PARM_DECL.
PR c++/14173
* semantics.c (begin_class_definition): Set TYPE_PACKED correctly
for all type variants.
PR c++/14173
* g++.dg/ext/packed5.C: New test.
PR c++/14199
* g++.dg/warn/Wunused-5.C: New test.
PR c++/13927
* decl.c (duplicate_decls): Return error_mark_node for invalid
redeclarations.
* name-lookup.c (push_namespace): Ignore the return value from
pushdecl.
* pt.c (push_template_decl_real): Robustify.
PR c++/13927
* g++.dg/other/error8.C: Remove XFAIL markers.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.3962&r2=1.3963
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/decl.c.diff?cvsroot=gcc&r1=1.1187&r2=1.1188
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/name-lookup.c.diff?cvsroot=gcc&r1=1.39&r2=1.40
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/pt.c.diff?cvsroot=gcc&r1=1.830&r2=1.831
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/semantics.c.diff?cvsroot=gcc&r1=1.388&r2=1.389
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.3523&r2=1.3524
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/ext/packed5.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/other/error8.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/warn/Wunused-5.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13927
next prev parent reply other threads:[~2004-02-20 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 6:23 [Bug c++/13927] New: confusing error message on ibad " mec dot gnu at mindspring dot com
2004-01-30 12:22 ` [Bug c++/13927] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-02-02 19:23 ` [Bug c++/13927] [3.4/3.5 Regression] confusing error message on bad " giovannibajo at libero dot it
2004-02-02 20:43 ` giovannibajo at libero dot it
2004-02-14 2:12 ` cvs-commit at gcc dot gnu dot org
2004-02-14 2:15 ` cvs-commit at gcc dot gnu dot org
2004-02-14 2:17 ` cvs-commit at gcc dot gnu dot org
2004-02-14 2:19 ` cvs-commit at gcc dot gnu dot org
2004-02-14 2:23 ` [Bug c++/13927] [3.4/3.5 Regression] duplicated " giovannibajo at libero dot it
2004-02-20 7:33 ` mmitchel at gcc dot gnu dot org
2004-02-20 8:57 ` cvs-commit at gcc dot gnu dot org [this message]
2004-02-20 8:58 ` 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=20040220085743.5861.qmail@sources.redhat.com \
--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).