public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ethouris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52008] [Core/1495] ICE when adding partial specialization for variadic-templated structure
Date: Tue, 06 Nov 2012 23:32:00 -0000	[thread overview]
Message-ID: <bug-52008-4-XrVl5A9iU8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52008-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #14 from Michal Malecki <ethouris at gmail dot com> 2012-11-06 23:32:36 UTC ---
(In reply to comment #13)
> if the DR makes it ill-formed and GCC rejects it is this FIXED?

GCC "rejects" it by doing ICE. I don't think this is the right thing that GCC
should do.

My last proposal is: gcc should report error at the place where the wannabe
specialization is defined (comment with "line 18") with something like: "18:
This template specialization does not match the template parameters\n12: of
this class template". I cannot check whether gcc currently fixed to do this, so
I'm sorry if this is behind the current state.


  parent reply	other threads:[~2012-11-06 23:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 10:44 [Bug c++/52008] New: [C++0x] " ethouris at gmail dot com
2012-01-26 13:03 ` [Bug c++/52008] " rguenth at gcc dot gnu.org
2012-04-16 16:51 ` jason at gcc dot gnu.org
2012-04-17  2:33 ` jason at gcc dot gnu.org
2012-04-17 15:38 ` jason at gcc dot gnu.org
2012-04-20 13:33 ` ethouris at gmail dot com
2012-04-20 15:40 ` paolo.carlini at oracle dot com
2012-04-21  1:48 ` jason at gcc dot gnu.org
2012-04-21 12:07 ` ethouris at gmail dot com
2012-04-21 13:08 ` jason at gcc dot gnu.org
2012-04-23 12:39 ` ethouris at gmail dot com
2012-11-06 19:24 ` daniel.kruegler at googlemail dot com
2012-11-06 20:12 ` [Bug c++/52008] [Core/1495] " paolo.carlini at oracle dot com
2012-11-06 21:05 ` redi at gcc dot gnu.org
2012-11-06 23:32 ` ethouris at gmail dot com [this message]
2012-11-07  0:09 ` redi at gcc dot gnu.org
2012-11-07  7:18 ` ethouris at gmail dot com
2012-11-07 11:08 ` paolo.carlini at oracle dot com
2012-11-07 18:34 ` paolo.carlini at oracle dot com
2013-02-14 21:08 ` redi at gcc dot gnu.org

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-52008-4-XrVl5A9iU8@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).