public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: reichelt@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: c++/8522 Date: Wed, 22 Jan 2003 23:26:00 -0000 [thread overview] Message-ID: <20030122232603.22239.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8522; it has been noted by GNATS. From: reichelt@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Cc: Subject: c++/8522 Date: 22 Jan 2003 23:21:52 -0000 CVSROOT: /cvs/gcc Module name: gcc Changes by: reichelt@gcc.gnu.org 2003-01-22 23:21:51 Modified files: gcc/testsuite : ChangeLog Added files: gcc/testsuite/g++.dg/parse: ret-type1.C tmpl-outside1.C int-as-enum1.C no-typename1.C no-value1.C wrong-inline1.C ref1.C attr-ctor1.C namespace5.C func-def1.C undefined1.C specialization1.C struct-as-enum1.C undefined2.C Log message: PR c++/2738 * g++.dg/parse/ret-type1.C: New test. PR c++/3792 * g++.dg/parse/tmpl-outside1.C: New test. PR c++/4207 * g++.dg/parse/int-as-enum1.C: New test. PR c++/4903 * g++.dg/parse/no-typename1.C: New test. PR c++/5533 * g++.dg/parse/no-value1.C: New test. PR c++/5921 * g++.dg/parse/wrong-inline1.C: New test. PR c++/6402 * g++.dg/parse/ref1.C: New test. PR c++/6992 * g++.dg/parse/attr-ctor1.C: New test. PR c++/7229 * g++.dg/parse/namespace5.C: New test. PR c++/7917 * g++.dg/parse/func-def1.C: New test. PR c++/8143 * g++.dg/parse/undefined1.C: New test. PR c++/5723, PR c++/8522 * g++.dg/parse/specialization1.C: New test. PR c++/163, PR c++/8595 * g++.dg/parse/struct-as-enum1.C: New test. PR c++/9173 * g++.dg/parse/undefined2.C: New test. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.2361&r2=1.2362 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/ret-type1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/tmpl-outside1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/int-as-enum1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/no-typename1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/no-value1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/wrong-inline1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/ref1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/attr-ctor1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/namespace5.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/func-def1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/undefined1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/specialization1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/struct-as-enum1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/undefined2.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
reply other threads:[~2003-01-22 23:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030122232603.22239.qmail@sources.redhat.com \ --to=reichelt@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).