public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "grigory at stl dot sarov dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/12700] New: [g++ 3.4] ICE in size_binop Date: Tue, 21 Oct 2003 07:11:00 -0000 [thread overview] Message-ID: <20031021055241.12700.grigory@stl.sarov.ru> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12700 Summary: [g++ 3.4] ICE in size_binop Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: grigory at stl dot sarov dot ru CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-redhat-linux GCC host triplet: i686-redhat-linux GCC target triplet: i686-redhat-linux Yet another ICE related to covariant thunks. G++ 3.4 gives it on the the test- case listed below. This happens both on i686-redhat-linux and ia64-suse-linux. $ g++ -c ice-2.cpp ice-2.cpp:19: internal compiler error: in size_binop, at fold-const.c:1489 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. $ cat ice-2.cpp struct c2 { int i; }; struct c1 { virtual c2& f8() {}; }; struct c3 : c1, c2 { virtual c2& f8() {}; }; struct c11 : public c1 { virtual c3& f8() {}; }; struct c15 : virtual c3 { virtual c2& f8() {}; }; struct c18 : virtual c11 { virtual c15& f8(); }; c15& c18::f8() { throw 0; };
next reply other threads:[~2003-10-21 5:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-21 7:11 grigory at stl dot sarov dot ru [this message] 2003-10-21 13:47 ` [Bug c++/12700] ICE in size_binop with covariant return types bangerth at dealii dot org 2003-10-21 13:58 ` nathan at gcc dot gnu dot org 2003-10-24 8:12 ` nathan at gcc dot gnu dot org 2003-12-04 9:47 ` 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=20031021055241.12700.grigory@stl.sarov.ru \ --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).