public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lk1@teamten.com To: gcc-gnats@gcc.gnu.org Subject: c++/10428: struct <typedef'ed name> causes internal error Date: Thu, 17 Apr 2003 22:46:00 -0000 [thread overview] Message-ID: <20030417223815.30453.qmail@sources.redhat.com> (raw) >Number: 10428 >Category: c++ >Synopsis: struct <typedef'ed name> causes internal error >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Thu Apr 17 22:46:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Lawrence Kesteloot >Release: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) >Organization: >Environment: Linux neelypcx 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux >Description: Compile file in "How-To-Repeat" with "gcc foo.cpp". I get this error: foo.cpp:7: Internal compiler error in write_unscoped_name, at cp/mangle.c:782 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions. In another context (more complex), I got this error: /home/lawrence/src/include/ui.hpp:228: Internal error #20000521. /home/lawrence/src/include/ui.hpp:228: Internal compiler error in write_unscoped_name, at cp/mangle.c:782 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. This error doesn't happen if there's no namespace. >How-To-Repeat: namespace Name { typedef void *(*Function)( void *, int ); struct Foo { struct Function xyz[5]; }; } >Fix: The source supplied above is buggy (the "struct" shouldn't be there). But there shouldn't be a compiler error, either. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-17 22:46 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=20030417223815.30453.qmail@sources.redhat.com \ --to=lk1@teamten.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).