public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/89237] Partial specialization incorrectly marked as ambiguous
[not found] <bug-89237-4@http.gcc.gnu.org/bugzilla/>
@ 2021-12-14 3:32 ` pinskia at gcc dot gnu.org
2021-12-14 4:15 ` pinskia at gcc dot gnu.org
2024-01-23 20:25 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous with sizeof(T) narrowing down to bool jason at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-14 3:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89237
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
ICC also rejects it with the same message as GCC even.
MSVC rejects it with:
<source>(9): error C2794: 'type': is not a member of any direct or indirect
base class of 'enable_if<false,void>'
<source>(9): warning C4305: 'specialization': truncation from 'size_t' to
'bool'
If I change "sizeof(T)" to "sizeof(T)!=0" as what I thought the conversion
would be, then clang rejects it with the same error as GCC.
So I suspect it is rejecting the specialization due to the conversion from
size_t to bool which I thought I had saw a bug about that.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/89237] Partial specialization incorrectly marked as ambiguous
[not found] <bug-89237-4@http.gcc.gnu.org/bugzilla/>
2021-12-14 3:32 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous pinskia at gcc dot gnu.org
@ 2021-12-14 4:15 ` pinskia at gcc dot gnu.org
2024-01-23 20:25 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous with sizeof(T) narrowing down to bool jason at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-14 4:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89237
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=95564,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=87724
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
PR 95564 and PR 87724 are related. The issue is narrowing from a literal down
to bool.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/89237] Partial specialization incorrectly marked as ambiguous with sizeof(T) narrowing down to bool
[not found] <bug-89237-4@http.gcc.gnu.org/bugzilla/>
2021-12-14 3:32 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous pinskia at gcc dot gnu.org
2021-12-14 4:15 ` pinskia at gcc dot gnu.org
@ 2024-01-23 20:25 ` jason at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: jason at gcc dot gnu.org @ 2024-01-23 20:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89237
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Created attachment 57198
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57198&action=edit
WIP
Some WIP for this PR. But looking through IMPLICIT_CONV_EXPR unconditionally
breaks some testcases, and I don't want to spend any more time on this
non-regression in stage 4.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-01-23 20:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-89237-4@http.gcc.gnu.org/bugzilla/>
2021-12-14 3:32 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous pinskia at gcc dot gnu.org
2021-12-14 4:15 ` pinskia at gcc dot gnu.org
2024-01-23 20:25 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous with sizeof(T) narrowing down to bool jason at gcc dot gnu.org
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).