public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pgoverea@akamai.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/7761: gcc reports internal error code 383 on invalid namespace usage.
Date: Thu, 29 Aug 2002 09:16:00 -0000 [thread overview]
Message-ID: <20020829152258.7267.qmail@sources.redhat.com> (raw)
>Number: 7761
>Category: c++
>Synopsis: gcc reports internal error code 383 on invalid namespace usage.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: ice-on-illegal-code
>Submitter-Id: net
>Arrival-Date: Thu Aug 29 08:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: pgoverea@akamai.com
>Release: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>Organization:
>Environment:
Linux 2.2.12-20 i686 unknown
>Description:
~/src> gcc -v -save-temps test.cc
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/cpp -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=91 -D__ELF__ -Dunix -Di386 -D__i386__ -Dlinux -D__ELF__ -D__unix__ -D__i386__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux -Asystem(posix) -D__EXCEPTIONS -Asystem(unix) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__tune_i386__ test.cc test.ii
GNU CPP version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) (i386 Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
/usr/include/g++-2
/usr/local/include
/usr/i386-redhat-linux/include
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include
/usr/include
End of search list.
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/cc1plus test.ii -quiet -dumpbase test.cc -version -o test.s
GNU C++ version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) (i386-redhat-linux) compiled by GNU C version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release).
test.cc:4: Internal compiler error 383.
test.cc:4: Please submit a full bug report to `egcs-bugs@egcs.cygnus.com'.
test.cc:4: See <URL:http://egcs.cygnus.com/faq.html#bugreport> for details.
>How-To-Repeat:
compile file containing:
struct A { };
namespace A { struct B {}; }
using A::B;
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-08-29 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 9:16 pgoverea [this message]
2002-08-29 11:16 Gabriel Dos Reis
2002-09-13 13:53 nathan
2002-09-13 13:54 nathan
2002-10-31 13:33 bangerth
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=20020829152258.7267.qmail@sources.redhat.com \
--to=pgoverea@akamai.com \
--cc=gcc-gnats@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).