public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/16706] [3.4/3.5 Regression] ICE in finish_member_declaration, at cp/semantics.c:2126 Date: Mon, 02 Aug 2004 20:38:00 -0000 [thread overview] Message-ID: <20040802203855.3926.qmail@sourceware.org> (raw) In-Reply-To: <20040725152539.16706.debian-gcc@lists.debian.org> ------- Additional Comments From reichelt at gcc dot gnu dot org 2004-08-02 20:38 ------- > Volker's reduced code > : Search converges between 2003-01-15-trunk (#165) and 2003-01-17-trunk (#166). > > Wolfgang's reduced code > : Search converges between 2003-10-17-trunk (#379) and 2003-10-18-trunk (#380). > > So they look like two different bugs. I still think this is the same underlying bug: a) I reduced Wolfgang's version to come up with mine. b) My example starts with an ICE in cxx_incomplete_type_diagnostic, at cp/typeck2.c:278 which changed to instantiate_class_template, at cp/pt.c:5440 the day Wolfgang's testcase started crashing the compiler. Btw, I've got another reduced example - this time the crash is in the same spot as with the original example. For this one I also get : Search converges between 2003-01-15-trunk (#165) and 2003-01-17-trunk (#166). =============================================================================== template<typename> struct A { struct X; struct Y; }; template<typename T> struct B { T t; B(); }; template<typename T> struct C { B<A<T> > b; template<typename> struct D; }; template<typename T> template<typename U> struct C<T>::D<U*> { B<A<T> > b; D() {} }; template struct C<int>::D<int*>; =============================================================================== -- What |Removed |Added ---------------------------------------------------------------------------- CC| |reichelt at gcc dot gnu dot | |org Keywords| |monitored http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16706
next prev parent reply other threads:[~2004-08-02 20:38 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-25 15:25 [Bug c++/16706] New: " debian-gcc at lists dot debian dot org 2004-07-25 15:27 ` [Bug c++/16706] " debian-gcc at lists dot debian dot org 2004-07-25 18:07 ` [Bug c++/16706] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-26 0:54 ` bangerth at dealii dot org 2004-07-26 3:18 ` reichelt at gcc dot gnu dot org 2004-07-29 14:40 ` pinskia at gcc dot gnu dot org 2004-07-29 14:50 ` bangerth at dealii dot org 2004-08-01 15:08 ` lerdsuwa at gcc dot gnu dot org 2004-08-02 20:38 ` reichelt at gcc dot gnu dot org [this message] 2004-08-02 21:06 ` reichelt at gcc dot gnu dot org 2004-08-03 15:25 ` lerdsuwa at gcc dot gnu dot org 2004-08-10 20:27 ` Woebbeking at web dot de 2004-08-16 15:49 ` lerdsuwa at gcc dot gnu dot org 2004-08-23 19:23 ` mmitchel at gcc dot gnu dot org 2004-08-24 14:14 ` cvs-commit at gcc dot gnu dot org 2004-08-24 14:32 ` cvs-commit at gcc dot gnu dot org 2004-08-24 14:36 ` lerdsuwa at gcc dot gnu dot org 2004-08-24 14:36 ` 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=20040802203855.3926.qmail@sourceware.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).