public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: hg211@ural2.hszk.bme.hu To: gcc-gnats@gcc.gnu.org Subject: c++/10223: template trickery causes ICE (segmentation fault) Date: Wed, 26 Mar 2003 14:56:00 -0000 [thread overview] Message-ID: <20030326141651.31563.qmail@sources.redhat.com> (raw) >Number: 10223 >Category: c++ >Synopsis: template trickery causes ICE (segmentation fault) >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Wed Mar 26 14:26:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Geza Herman >Release: All gcc versions >Organization: >Environment: Linux 2.4.18 i686 Debian GNU/Linux >Description: The code sample causes ICE an all gcc versions I tried: gcc version 2.95.4 20011002 (Debian prerelease) gcc version 3.0.4 gcc version 3.2.3 20030316 (Debian prerelease) gcc version 3.3 20030314 (prerelease) The sample tries to get some meta-information: tries to determine if a class has a particular member-function. ('void save()' in this example) >How-To-Repeat: compile this sample: template <typename T> class hasSaveFunction { private: struct Helper { struct False { char dummy[1979]; }; template <void (T::*)()> struct dummy; template <typename T2> static char test(dummy<&T2::save> *); template <typename T2> static False test(...); }; public: static const bool value = sizeof(Helper::template test<T>(0))==1 ; }; class Dummy { }; int main() { return hasSaveFunction<Dummy>::value; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-26 14:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-26 14:56 hg211 [this message] 2003-03-26 15:28 bangerth 2003-03-27 21:56 Volker Reichelt 2003-05-02 17:36 Giovanni Bajo
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=20030326141651.31563.qmail@sources.redhat.com \ --to=hg211@ural2.hszk.bme.hu \ --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).