https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.0
--- Comment #14 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #13 from Ville Voutilainen ---
Right, that was fixed in the immediately following revision,
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=236823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #12 from Andreas Krebbel ---
(In reply to Ville Voutilainen from comment #11)
> I don't see how any of that code or the failure is in any way related to
> std::tuple...
This was the wrong error message. The bootstrap problem trigger
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #11 from Ville Voutilainen ---
I don't see how any of that code or the failure is in any way related to
std::tuple...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
Andreas Krebbel changed:
What|Removed |Added
CC||krebbel at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #9 from ville at gcc dot gnu.org ---
Author: ville
Date: Fri May 27 14:08:37 2016
New Revision: 236822
URL: https://gcc.gnu.org/viewcvs?rev=236822&root=gcc&view=rev
Log:
2016-05-24 Ville Voutilainen
PR libstdc++/66338
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #8 from Ville Voutilainen ---
Patch available: https://gcc.gnu.org/ml/gcc-patches/2016-05/msg01914.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #7 from Ville Voutilainen ---
Not so simple, still working on this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #6 from Ville Voutilainen ---
Should be a simple matter of doing the _NonNestedTuple checks before other
checks. Patch coming in a couple of days.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
Ville Voutilainen changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #4 from Jonathan Wakely ---
(In reply to Pawel Tomulik from comment #2)
> Anyway, adding explicit to S(T&&) solves the problem...
Or constrain your greedy template so it only accepts arguments that can be
assigned to S::i_
struct S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #3 from Jonathan Wakely ---
I think this is expected, because your type S has an unconstrained constructor
template that accepts any argument, including objects of type tuple, but in
the signature of that constructor (specifically in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #2 from Pawel Tomulik ---
I found this to be related to std::tuple constructors, especially this one:
template...>::value>::type>
explicit
constexpr tuple(_UElements&&... __elements)
: _Inherited(std::fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66338
--- Comment #1 from Pawel Tomulik ---
As a side note, the following variant also does not compile:
int main()
{
15 matches
Mail list logo