public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4926: Segmentation Fault on Legal Code Date: Fri, 01 Nov 2002 12:36:00 -0000 [thread overview] Message-ID: <20021101203601.20440.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4926; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/4926: Segmentation Fault on Legal Code Date: Fri, 1 Nov 2002 14:31:33 -0600 (CST) It's too bad that templates with typeof are still broken in some places, since the (standards conforming) workarounds are also not working always. Here's a redux of PR 4926: -------------------------------------- template <unsigned> struct X { typedef int Type; }; template <typename T> struct Y { char array[1]; }; template<typename T> Y<T> P(T); // acts as "Y<typeof(T)>" struct F { int operator()() const; }; template <typename T> typename X<sizeof(P( T()() ).array)>::Type foo(); int main() { foo<F>(); }; -------------------------------------- By changing F::operator() into a "regular" member function, all sorts of other bugs can be triggered before the compiler finally crashed :-( Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-01 20:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-01 12:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-25 9:39 nathan 2001-11-18 14:16 anthwil
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=20021101203601.20440.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).