public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gereon.kremer at cs dot rwth-aachen.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59759] internal compiler error: in unify, using std::enable_if on classes
Date: Tue, 26 May 2015 11:44:00 -0000 [thread overview]
Message-ID: <bug-59759-4-UPe4kpdLMY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59759-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59759
--- Comment #12 from Gereon Kremer <gereon.kremer at cs dot rwth-aachen.de> ---
And once again.
I just upgraded to gcc 5.1.0
Sure enough, it's not fixed...
Test_GCC.cpp: In substitution of ‘template<class T> void f(const A<T>*) [with T
= <missing>]’:
Test_GCC.cpp:25:7: required from here
Test_GCC.cpp:25:7: internal compiler error: in unify, at cp/pt.c:18571
f(map);
>From gcc-bugs-return-487282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 26 11:50:11 2015
Return-Path: <gcc-bugs-return-487282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69398 invoked by alias); 26 May 2015 11:50:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69187 invoked by uid 48); 26 May 2015 11:49:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66289] New: [5/6 Regression] "error: ambiguous template instantiation" with partial specialization defined in terms of alias template
Date: Tue, 26 May 2015 11:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-66289-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg02122.txt.bz2
Content-length: 1708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66289
Bug ID: 66289
Summary: [5/6 Regression] "error: ambiguous template
instantiation" with partial specialization defined in
terms of alias template
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
5.1 and later incorrectly reject this, but it should compile because
foo<shared_ptr<A<T>>> is more specialized than foo<shared_ptr<T>>:
template<typename T> struct A {};
template<typename T> struct shared_ptr { };
template<typename T> using APtr = shared_ptr<A<T>>;
template<typename T> struct foo;
template<typename T> struct foo<shared_ptr<T>> { };
template<typename T> struct foo<APtr<T>> { };
foo<shared_ptr<A<int>>> aa;
amb.cc:10:25: error: ambiguous template instantiation for ‘struct
foo<shared_ptr<A<int> > >’
foo<shared_ptr<A<int>>> aa;
^
amb.cc:7:29: note: candidates are: template<class T> struct foo<shared_ptr<T> >
[with T = A<int>]
template<typename T> struct foo<shared_ptr<T>> { };
^
amb.cc:8:29: note: template<class T> struct foo<APtr<T> > [with
T = int]
template<typename T> struct foo<APtr<T>> { };
^
amb.cc:10:25: error: aggregate ‘foo<shared_ptr<A<int> > > aa’ has incomplete
type and cannot be defined
foo<shared_ptr<A<int>>> aa;
^
>From gcc-bugs-return-487283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 26 11:51:28 2015
Return-Path: <gcc-bugs-return-487283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71940 invoked by alias); 26 May 2015 11:51:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70004 invoked by uid 48); 26 May 2015 11:51:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66289] [5/6 Regression] "error: ambiguous template instantiation" with partial specialization defined in terms of alias template
Date: Tue, 26 May 2015 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-66289-4-FwrF64xVJI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66289-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66289-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg02123.txt.bz2
Content-length: 523
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf289
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-05-26
Known to work| |4.8.3, 4.9.2
Ever confirmed|0 |1
Known to fail| |5.1.0, 6.0
next prev parent reply other threads:[~2015-05-26 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 16:21 [Bug c++/59759] New: " gereon.kremer at cs dot rwth-aachen.de
2014-01-10 16:21 ` [Bug c++/59759] " gereon.kremer at cs dot rwth-aachen.de
2014-01-10 16:36 ` mpolacek at gcc dot gnu.org
2014-01-10 16:43 ` gereon.kremer at cs dot rwth-aachen.de
2014-01-15 10:30 ` gereon.kremer at cs dot rwth-aachen.de
2014-04-10 14:55 ` paolo.carlini at oracle dot com
2014-09-26 14:40 ` gereon.kremer at cs dot rwth-aachen.de
2014-09-26 15:02 ` trippels at gcc dot gnu.org
2014-09-30 13:26 ` trippels at gcc dot gnu.org
2014-11-26 15:09 ` gereon.kremer at cs dot rwth-aachen.de
2014-11-26 15:13 ` trippels at gcc dot gnu.org
2014-12-22 20:57 ` ktietz at gcc dot gnu.org
2015-05-26 11:44 ` gereon.kremer at cs dot rwth-aachen.de [this message]
2015-05-26 12:07 ` ktietz 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-59759-4-UPe4kpdLMY@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).