public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/47311] [C++0x] ICE in tsubst @cp/pt.c:10502
Date: Sun, 16 Jan 2011 03:15:00 -0000 [thread overview]
Message-ID: <bug-47311-4-grQY3h4Cu2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47311-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47311
Pawel Sikora <pluto at agmk dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dodji at gcc dot gnu.org
--- Comment #14 from Pawel Sikora <pluto at agmk dot net> 2011-01-16 02:16:59 UTC ---
0d432ee0d0d07e9c17b69e06afc1be9d65f57546 is the first bad commit:
commit 0d432ee0d0d07e9c17b69e06afc1be9d65f57546
Author: dodji <dodji@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Tue Nov 2 12:44:19 2010 +0000
Restore canonical type comparison for dependent type(def)s
This patch restores canonical type comparison for dependent types and
then dependent typedefs. After this patch, two template type
parameters T are equal if they have the same index, level, *and*
number of sibling parameters. The novelty is to take in account the
number of sibling parameters.
To do this we first build the template parameters w/o taking in
account their number of siblings. When we know the number of template
parameters we fix up each template parameter with the number of
slibling parameters and we build the appropriate canonical types
accordingly. The patch fixes the fallouts deemed necessary.
This fixes PR c++/45606 but actually fixes all the previous bugs
related to dependent typedef comparison we had since we started to
properly representing dependent typedefs.
next prev parent reply other threads:[~2011-01-16 2:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 22:53 [Bug c++/47311] New: " pluto at agmk dot net
2011-01-15 23:16 ` [Bug c++/47311] " hjl.tools at gmail dot com
2011-01-15 23:18 ` hjl.tools at gmail dot com
2011-01-15 23:20 ` pluto at agmk dot net
2011-01-15 23:27 ` pluto at agmk dot net
2011-01-16 0:19 ` pluto at agmk dot net
2011-01-16 0:38 ` pluto at agmk dot net
2011-01-16 1:05 ` hjl.tools at gmail dot com
2011-01-16 1:09 ` pluto at agmk dot net
2011-01-16 1:24 ` pluto at agmk dot net
2011-01-16 1:36 ` [Bug preprocessor/47311] " hjl.tools at gmail dot com
2011-01-16 1:36 ` zsojka at seznam dot cz
2011-01-16 1:53 ` pluto at agmk dot net
2011-01-16 2:04 ` zsojka at seznam dot cz
2011-01-16 3:15 ` pluto at agmk dot net [this message]
2011-01-17 16:08 ` [Bug preprocessor/47311] [4.6 Regression][C++0x] " rth at gcc dot gnu.org
2011-01-17 18:39 ` pluto at agmk dot net
2011-01-17 19:18 ` rth at gcc dot gnu.org
2011-01-17 19:59 ` pluto at agmk dot net
2011-01-17 20:07 ` andi-gcc at firstfloor dot org
2011-01-17 20:09 ` jakub at gcc dot gnu.org
2011-01-18 14:28 ` hjl.tools at gmail dot com
2011-01-18 14:44 ` jakub at gcc dot gnu.org
2011-01-20 10:44 ` dodji at gcc dot gnu.org
2011-01-20 10:47 ` dodji at gcc dot gnu.org
2011-01-20 16:37 ` dodji at gcc dot gnu.org
2011-01-22 13:54 ` pluto at agmk dot net
2011-01-25 23:05 ` dodji at gcc dot gnu.org
2011-01-28 23:01 ` pluto at agmk dot net
2011-01-29 7:07 ` dodji at gcc dot gnu.org
2011-01-29 7:16 ` dodji at gcc dot gnu.org
2011-02-02 18:20 ` dnovillo 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-47311-4-grQY3h4Cu2@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).