public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rguenth@tat.physik.uni-tuebingen.de To: gcc-gnats@gcc.gnu.org Subject: c++/9432: [3.4 regression] ICE in validate_nonmember_using_decl, at cp/decl2.c:4152 Date: Fri, 24 Jan 2003 11:16:00 -0000 [thread overview] Message-ID: <20030124110731.7812.qmail@sources.redhat.com> (raw) >Number: 9432 >Category: c++ >Synopsis: [3.4 regression] ICE in validate_nonmember_using_decl, at cp/decl2.c:4152 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Fri Jan 24 11:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Richard Guenther >Release: g++-3.4 (GCC) 3.4 20030124 (experimental) >Organization: >Environment: ix86-linux >Description: The following testcase ICEs with using2.cpp: In member function `void Bar<T>::foo()': using2.cpp:6: internal compiler error: in validate_nonmember_using_decl, at cp/decl2.c:4152 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Maybe this is even legal ISO C++? Pulling the using declaration to class scope makes the ICE go away. Previous (old parser) g++ give a parse error on the code, my available EDG based compiler (intel icpc) ICEs, too. template <class T> struct Foo; template <class T> struct Bar : public Foo<T> { void foo() { using Foo<T>::i; } }; >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-01-24 11:16 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=20030124110731.7812.qmail@sources.redhat.com \ --to=rguenth@tat.physik.uni-tuebingen.de \ --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).