public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tdegrange@nexwave-solutions.com To: gcc-gnats@gcc.gnu.org Subject: c++/3123: A class derivated from a namespace causes an internal compiler error Date: Mon, 11 Jun 2001 09:46:00 -0000 [thread overview] Message-ID: <20010611163732.27749.qmail@sourceware.cygnus.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1163 bytes --] >Number: 3123 >Category: c++ >Synopsis: A class derivated from a namespace causes an internal compiler error >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Mon Jun 11 09:46:03 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Thomas Dégrange >Release: Regcc version 2.95.3 19991030 (prerelease) >Organization: >Environment: >Description: > gcc -v Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.3/specs gcc version 2.95.3 19991030 (prerelease) "The following code causes an GCC internal error on my system and seems to be accepted on "CodeSourcery's Online Test Compilation". In both cases it seems to me that GCC has a bug." > g++ main.cc main.cc:6: Internal compiler error. main.cc:6: Please submit a full bug report. main.cc:6: See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. >How-To-Repeat: file "main.cc": namespace Out { namespace In { } } class Class : public Out::In { }; >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-11 9:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-11 9:46 tdegrange [this message] 2001-08-11 12:56 gdr 2002-03-16 5:06 rodrigc
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=20010611163732.27749.qmail@sourceware.cygnus.com \ --to=tdegrange@nexwave-solutions.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: 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).