public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/86142] hard error for bad delete-expression in SFINAE context
[not found] <bug-86142-4@http.gcc.gnu.org/bugzilla/>
@ 2020-05-12 16:08 ` ppalka at gcc dot gnu.org
2020-05-15 2:30 ` ensadc at mailnesia dot com
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: ppalka at gcc dot gnu.org @ 2020-05-12 16:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86142
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Looks ever since r10-2197, GCC 10 correctly performs SFINAE for the first two
overloaded calls.
But could you explain why
int z = f<void*>();
should resolve to the second overload of f?
My understanding is that 'delete' on a pointer to void is undefined behavior,
but is not ill-formed, so there is no substitution failure and we should select
the first overload.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c++/86142] hard error for bad delete-expression in SFINAE context
[not found] <bug-86142-4@http.gcc.gnu.org/bugzilla/>
2020-05-12 16:08 ` [Bug c++/86142] hard error for bad delete-expression in SFINAE context ppalka at gcc dot gnu.org
@ 2020-05-15 2:30 ` ensadc at mailnesia dot com
2020-05-19 22:42 ` ensadc at mailnesia dot com
2020-05-20 9:32 ` redi at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: ensadc at mailnesia dot com @ 2020-05-15 2:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86142
--- Comment #2 from ensadc at mailnesia dot com ---
I was misled by Clang. Seems like there's a Clang bug then.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c++/86142] hard error for bad delete-expression in SFINAE context
[not found] <bug-86142-4@http.gcc.gnu.org/bugzilla/>
2020-05-12 16:08 ` [Bug c++/86142] hard error for bad delete-expression in SFINAE context ppalka at gcc dot gnu.org
2020-05-15 2:30 ` ensadc at mailnesia dot com
@ 2020-05-19 22:42 ` ensadc at mailnesia dot com
2020-05-20 9:32 ` redi at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: ensadc at mailnesia dot com @ 2020-05-19 22:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86142
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Known to work| |10.1.0
Known to fail| |9.3.0
Resolution|--- |FIXED
--- Comment #3 from ensadc at mailnesia dot com ---
Fixed in GCC 10
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c++/86142] hard error for bad delete-expression in SFINAE context
[not found] <bug-86142-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2020-05-19 22:42 ` ensadc at mailnesia dot com
@ 2020-05-20 9:32 ` redi at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2020-05-20 9:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86142
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
Version|unknown |9.3.0
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-05-20 9:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-86142-4@http.gcc.gnu.org/bugzilla/>
2020-05-12 16:08 ` [Bug c++/86142] hard error for bad delete-expression in SFINAE context ppalka at gcc dot gnu.org
2020-05-15 2:30 ` ensadc at mailnesia dot com
2020-05-19 22:42 ` ensadc at mailnesia dot com
2020-05-20 9:32 ` redi 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).