public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pepster at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/15862] New: 'enum yn' fails
Date: Mon, 07 Jun 2004 22:04:00 -0000 [thread overview]
Message-ID: <20040607220413.15862.pepster@users.sourceforge.net> (raw)
This short code snippet fails to compile. Worked in 3.3.
As far as I can tell, yn is not a reserved word.
--------------------
enum yn {Y, N};
enum yn x = Y;
--------------------
g++ -v -c x.cc
Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/specs
Configured with: ../gcc-3.4.0/configure --enable-languafes=c,c++
Thread model: posix
gcc version 3.4.0
/usr/local/libexec/gcc/i686-pc-linux-gnu/3.4.0/cc1plus -quiet -v -D_GNU_SOURCE
x.cc -quiet -dumpbase x.cc -mtune=pentiumpro -auxbase x -version -o /tmp/cccljUxr.s
ignoring nonexistent directory "NONE/include"
ignoring nonexistent directory
"/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0
/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0/i686-pc-linux-gnu
/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0/backward
/usr/local/include
/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/include
/usr/include
End of search list.
GNU C++ version 3.4.0 (i686-pc-linux-gnu)
compiled by GNU C version 3.4.0.
GGC heuristics: --param ggc-min-expand=45 --param ggc-min-heapsize=29906
x.cc:2: error: use of enum `yn' without previous declaration
x.cc:2: error: invalid type in declaration before '=' token
$ uname -a
Linux yoda 2.4.18-18.8.0 #1 Wed Nov 13 22:52:09 EST 2002 i686 athlon i386 GNU/Linux
--
Summary: 'enum yn' fails
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pepster at users dot sourceforge dot net
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15862
next reply other threads:[~2004-06-07 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 22:04 pepster at users dot sourceforge dot net [this message]
2004-06-07 22:23 ` [Bug c++/15862] [3.4/4.5 Regression] " pinskia at gcc dot gnu dot org
2004-06-07 22:33 ` bangerth at dealii dot org
2004-06-07 22:38 ` pinskia at gcc dot gnu dot org
2004-06-07 22:44 ` bangerth at dealii dot org
2004-06-09 16:33 ` mmitchel at gcc dot gnu dot org
2004-06-10 14:42 ` mmitchel at gcc dot gnu dot org
2004-06-11 18:15 ` cvs-commit at gcc dot gnu dot org
2004-06-11 18:18 ` cvs-commit at gcc dot gnu dot org
2004-06-11 18:20 ` mmitchel at gcc dot gnu dot org
2005-05-22 20:44 ` pinskia 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=20040607220413.15862.pepster@users.sourceforge.net \
--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).