https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
Markus Trippelsdorf changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #14 from Alexander Kondratskiy ---
Stackoverflow question/answer:
http://stackoverflow.com/questions/35875829/template-parameters-not-deducible-in-partial-specialization-in-gcc6-for-a-case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
Barry Revzin changed:
What|Removed |Added
CC||barry.revzin at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #12 from Alexander Kondratskiy ---
Ok, I will ask stackoverflow.
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #11 from Markus Trippelsdorf ---
(In reply to Alexander Kondratskiy from comment #10)
> My issue is that this code was accepted since gcc 4.8 completely fine.
> Unless there is a specific line in the standard that prevents this from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #10 from Alexander Kondratskiy ---
My issue is that this code was accepted since gcc 4.8 completely fine. Unless
there is a specific line in the standard that prevents this from working, I
don't understand how appealing to potential
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #9 from Markus Trippelsdorf ---
There is really no need to take another look.
When your testcase generates a warning under clang and also gets rejected by
MSVC, it is obvious that there is something wrong with it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #8 from Alexander Kondratskiy ---
I'm sorry Markus, but "clang issues a warning" is not a good enough reason to
mark this invalid. By the same token, the warning in clang could have been
introduced "because gcc issues an error". What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #7 from Alexander Kondratskiy ---
To add some color, maybe this is related to non-deduced contexts from
14.8.2.5p5 in the standard:
The non-deduced contexts are:
— The nested-name-specifier of a type that was specified using a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
Markus Trippelsdorf changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #2 from Alexander Kondratskiy ---
Looking at the diffs in r229628 linked by Jakub, I find the changes to lines
8791 and 8793 in pt.c to be kinda fishy:
https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/cp/pt.c?r1=229628=229627=229628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P3
--- Comment #5 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #3 from Alexander Kondratskiy ---
Sorry, I take the "fishy" comment back. I'm not familiar enough with the code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
--- Comment #4 from Markus Trippelsdorf ---
I'm not sure this is a compiler bug at all.
Even clang warns:
foo.ii:10:32: warning: class template partial specialization contains a
template parameter that cannot be deduced; this partial
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70141
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
15 matches
Mail list logo
