public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51385] Unnecessary instantiation converting to pointer to template class instance
Date: Fri, 02 Dec 2011 10:36:00 -0000	[thread overview]
Message-ID: <bug-51385-4-2bYXFmEWXn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51385-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51385

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-12-02 10:36:14 UTC ---
Here's a version which isn't a compile-time-hog but demonstrates the
unnecessary instantiation with a static_assert (so needs -std=c++11)


template <unsigned N> struct NTmpl;
template <typename T, typename U, typename V = NTmpl<sizeof(T *)> >
struct PtrConvs {
   enum { bad = 1 };
};

template <typename Target, typename Source>
struct PtrConvs<Target, Source, NTmpl<sizeof (*(Target **)0 = (Source *)0)> >;

template<typename T> struct test { static const bool value = true; };
template<> struct test<short> { static const bool value = false; };

template <typename T>
struct FussyTemplate
{
    static_assert( test<T>::value, "not short" );
};

struct B { };

typedef char chk[1];
typedef char chk[PtrConvs<FussyTemplate<short>, B>::bad];


EFG and Clang compile this happily, without instantiating FussyTemplate<short>


  reply	other threads:[~2011-12-02 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 23:32 [Bug c++/51385] New: " hstong at ca dot ibm.com
2011-12-02 10:36 ` redi at gcc dot gnu.org [this message]
2011-12-02 10:43 ` [Bug c++/51385] " paolo.carlini at oracle dot com
2011-12-02 10:48 ` redi at gcc dot gnu.org
2014-09-29  8:55 ` paolo.carlini at oracle dot com
2014-09-29  9:07 ` paolo at gcc dot gnu.org
2014-09-29  9:08 ` paolo.carlini at oracle dot com

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=bug-51385-4-2bYXFmEWXn@http.gcc.gnu.org/bugzilla/ \
    --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: link
Be 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).