public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: peter@peem.als.lbl.gov To: gcc-gnats@gcc.gnu.org Subject: c++/9820: ice in build_baselink (templates) Date: Mon, 24 Feb 2003 06:26:00 -0000 [thread overview] Message-ID: <200302240621.h1O6LhKn013295@peem.als.lbl.gov> (raw) >Number: 9820 >Category: c++ >Synopsis: ice in build_baselink (templates) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Feb 24 06:26:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Peter Schmid >Release: 3.4 20030216 (experimental) >Organization: LBNL >Environment: System: Linux linux 2.4.19-4GB #1 Wed Nov 27 00:56:40 UTC 2002 i686 unknown Architecture: i686 SuSE 8.1 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc/configure --enable-threads=posix --enable-languages=c,c++,f77,objc --enable-__cxa_atexit --disable-nls >Description: The following IMHO legal input source generates an ice. The input source is a stripped-down version of the file types/types.cpp included in the book "C++ Templates: The Complete Guide" by Vandevoorde and Josuttis. >How-To-Repeat: source code t.C template<typename T> class IsFunctionT { private: typedef char One; typedef struct { char a[2]; } Two; template<typename U> static One test(...); template<typename U> static Two test(U (*)[1]); public: enum { Yes = sizeof(IsFunctionT<T>::template test<T>(0)) == 1 }; enum { No = !Yes }; }; template<typename T> class IsClassT { public: enum { Yes = IsFunctionT<T>::No}; enum { No = !Yes }; }; template <typename T> void check() { enum {Yes = IsClassT<T>::Yes}; } int main() { check<int>(); } Compiling t.C g++ -v -W -Wall t.C Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.4/specs Configured with: ../gcc/configure --enable-threads=posix --enable-languages=c,c++,f77,objc --enable-__cxa_atexit --disable-nls Thread model: posix gcc version 3.4 20030216 (experimental) /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.4/cc1plus -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=4 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE t.C -D__GNUG__=3 -quiet -dumpbase t.C -auxbase t -W -Wall -version -o /tmp/ccKZhGCG.s GNU C++ version 3.4 20030216 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 3.4 20030216 (experimental). ignoring nonexistent directory "NONE/include" ignoring nonexistent directory "/usr/local/i686-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include/c++/3.4 /usr/local/include/c++/3.4/i686-pc-linux-gnu /usr/local/include/c++/3.4/backward /usr/local/include /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.4/include /usr/include End of search list. t.C:2: warning: all member functions in class `IsFunctionT<T>' are private t.C: In instantiation of `IsFunctionT<int>': t.C:16: instantiated from `IsClassT<int>' t.C:23: instantiated from `void check() [with T = int]' t.C:29: instantiated from here t.C:9: internal compiler error: in build_baselink, at cp/search.c:1333 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-02-24 6:26 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=200302240621.h1O6LhKn013295@peem.als.lbl.gov \ --to=peter@peem.als.lbl.gov \ --cc=gcc-gnats@gcc.gnu.org \ --cc=poschmid@lbl.gov \ /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).