public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11076] New: ICE with invalid base class Date: Tue, 03 Jun 2003 09:36:00 -0000 [thread overview] Message-ID: <20030603093558.11076.reichelt@gcc.gnu.org> (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=11076 Summary: ICE with invalid base class Product: gcc Version: 3.4 Status: NEW Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: reichelt@gcc.gnu.org CC: gcc-bugs@gcc.gnu.org This is fallout from PR5702: The following code crashes gcc 2.95.x - 3.3 and mainline: ---------------------------------------------------------------- template<typename, typename T=void> struct A { typedef A<T,T> B; }; template <typename T> struct C { typedef typename A<T>::B X; X::Y; }; C<void> c; ---------------------------------------------------------------- The error message on mainline is: pr5702.cc: In instantiation of `C<void>': pr5702.cc:12: instantiated from here pr5702.cc:9: internal compiler error: tree check: accessed elt 2 of tree_vec with 1 elts in tsubst, at cp/pt.c:6697 Please submit a full bug report, ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2003-06-03 9:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-03 9:36 reichelt@gcc.gnu.org [this message] 2003-06-03 14:12 ` [Bug c++/11076] " bangerth@dealii.org 2003-06-22 13:10 ` pinskia at physics dot uc dot edu 2003-08-02 4:06 ` pinskia at physics dot uc dot edu 2003-10-21 14:52 ` lerdsuwa at gcc dot gnu dot org 2003-10-24 14:47 ` cvs-commit at gcc dot gnu dot org 2003-10-24 14:51 ` lerdsuwa 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=20030603093558.11076.reichelt@gcc.gnu.org \ --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).