public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/94771] New: g++.dg/concepts/diagnostic10.C fails on mingw
@ 2020-04-26  9:59 sbence92 at gmail dot com
  2020-04-27  7:32 ` [Bug c++/94771] " iains at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: sbence92 at gmail dot com @ 2020-04-26  9:59 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94771

            Bug ID: 94771
           Summary: g++.dg/concepts/diagnostic10.C fails on mingw
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sbence92 at gmail dot com
  Target Milestone: ---

g++.dg/concepts/diagnostic10.C fails with gcc 10 (ead1c27a530) on mingw target
and host.

Instead of 
diagnostic10.C:6:31: error: invalid use of non-static member function 'int
S::f()'
we get
diagnostic10.C:6:31: error: statement cannot resolve address of overloaded
function.

Seems like the fix for Bug 52597 (typeck.c invalid_nonstatic_memfn_p) went with
a special case for -fms-extensions which is a default for mingw.

Compiling with -fno-ms-extensions provides the correct diagnostic.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-04-28  8:07 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-26  9:59 [Bug c++/94771] New: g++.dg/concepts/diagnostic10.C fails on mingw sbence92 at gmail dot com
2020-04-27  7:32 ` [Bug c++/94771] " iains at gcc dot gnu.org
2020-04-27  8:30 ` redi at gcc dot gnu.org
2020-04-27  8:56 ` redi at gcc dot gnu.org
2020-04-28  8:07 ` sbence92 at gmail dot com

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).