public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pommier@gmm.insa-tlse.fr To: gcc-gnats@gcc.gnu.org Subject: c++/9261: Internal compiler error in arg_assoc, at cp/decl2.c:4793 Date: Fri, 10 Jan 2003 15:26:00 -0000 [thread overview] Message-ID: <20030110151622.17936.qmail@sources.redhat.com> (raw) >Number: 9261 >Category: c++ >Synopsis: Internal compiler error in arg_assoc, at cp/decl2.c:4793 >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Fri Jan 10 07:26:01 PST 2003 >Closed-Date: >Last-Modified: >Originator: julien pommier >Release: 3.2 , 3.2.1 >Organization: >Environment: Debian 3.0 Linux 2.4.18 i686 unknown / g++ (GCC) 3.2.1 OSF1 V4.0 1229 alpha / g++ (GCC) 3.2 >Description: The following (invalid) code: #include <iostream> #include <typeinfo> struct A { virtual void f() {} }; int main() { A* p; std::cerr << typeid(*p).name; } crashes g++ 3.2, g++ 3.2.1 (and also g++ 3.0) with this message: t.C: In function `int main()': t.C:9: Internal compiler error in arg_assoc, at cp/decl2.c:4809 it may be related to the (closed) bugreport #3416 for a crash of g++ 3.0 at the same place. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-01-10 15: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=20030110151622.17936.qmail@sources.redhat.com \ --to=pommier@gmm.insa-tlse.fr \ --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).