public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yanliu at ca dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/16980] New: internal compiler error: in cp_expr_size, at cp/cp-lang.c:330 Date: Wed, 11 Aug 2004 15:20:00 -0000 [thread overview] Message-ID: <20040811152000.16980.yanliu@ca.ibm.com> (raw) This is a regression from g++3.3. With g++3.3, the testcase passed, but with g++ 3.5, it failed with internal compiler error: t.C:11: warning: direct base `c4' inaccessible in `c15' due to ambiguity t.C:19: warning: `v3' initialized and declared `extern' t.C: In function `void __static_initialization_and_destruction_0(int, int)':internal compiler error: in cp_expr_size, at cp/cp-lang.c:330. I am using g++ 3.5 version on powerpc apple MacOS system. Using gcc3.3, I am getting this message without compiler abend. t.C:11: warning: direct base `c4' inaccessible in `c15' due to ambiguity t.C:19: warning: `v3' initialized and declared `extern' ld: Undefined symbols: _main __ZN3c17C1Ev ___gxx_personality_v0 -- Summary: internal compiler error: in cp_expr_size, at cp/cp- lang.c:330 Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: yanliu at ca dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: gcc version 3.5.0-tree-ssa 20040321 (merged 20040529) (Apple Com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16980
next reply other threads:[~2004-08-11 15:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-11 15:20 yanliu at ca dot ibm dot com [this message] 2004-08-11 15:22 ` [Bug c++/16980] " yanliu at ca dot ibm dot com 2004-08-11 15:43 ` [Bug c++/16980] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-08-11 17:40 ` bangerth at dealii dot org 2004-08-11 17:50 ` 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=20040811152000.16980.yanliu@ca.ibm.com \ --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: 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).