From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 148FA388F076; Wed, 6 May 2020 16:17:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 148FA388F076 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588781875; bh=7QUKjgFLX8GURVPIPpolXMOZ2KSJwv3Fm3kegy8XO08=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aHPoPjNnyPk2RVskO9fdfNsT8wddWs4fNQrNbLyND4i9P09b0Oqw8VES44g39iKvJ nlhJ3xN20ZCJuAMsoESOQL6O59OT6Ukctg5sEfnJg/G8zoS7Ub7UM2xgNciNz2N0N4 bFZc02y3EitBjxXANw0l4tb54Y7xlaVrJNbkQuw8= From: "db0451 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94973] compile error when trying to use pointer-to-member function as invokable projection to ranges::find() Date: Wed, 06 May 2020 16:17:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.3.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: db0451 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2020 16:17:55 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94973 --- Comment #8 from DB --- > I can reproduce it using x86_64-w64-mingw32-g++ 9.2.1 Thanks again for testing! > I'm not yet convinced this isn't a ranges-v3 bug. I will of course defer to your expertise! It could well be caused by someth= ing buried somewhere in range-v3's many layers of supporting code. If it can't = be a g++ bug, of course just say the word, and I will just forward this all to t= hem. > As it says on that page, "the first three of which can be obtained from t= he output of gcc -v" D'oh. Here we are: $ g++ -v Using built-in specs. COLLECT_GCC=3DC:\msys64\mingw64\bin\g++.exe COLLECT_LTO_WRAPPER=3DC:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9= .3.0/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../gcc-9.3.0/configure --prefix=3D/mingw64 --with-local-prefix=3D/mingw64/local --build=3Dx86_64-w64-mingw32 --host=3Dx86_64-w64-mingw32 --target=3Dx86_64-w64-mingw32 --with-native-system-header-dir=3D/mingw64/x86_64-w64-mingw32/include --libexecdir=3D/mingw64/lib --enable-bootstrap --with-arch=3Dx86-64 --with-tune=3Dgeneric --enable-languages=3Dc,lto,c++,fortran,ada,objc,obj-c= ++ --enable-shared --enable-static --enable-libatomic --enable-threads=3Dposix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts=3Dyes --enable-libstdcxx-time=3Dyes --disable-libstdcxx-pch --disable-libstdcxx-debug --disable-isl-version-che= ck --enable-lto --enable-libgomp --disable-multilib --enable-checking=3Drelease --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --enable-plugin --with-libiconv --with-system-zlib --with-gmp=3D/mingw64 --with-mpfr=3D/mingw64 --with-mpc=3D/mingw64 --with-isl=3D/mingw64 --with-pkgversion=3D'Rev2, Built by MSYS2 project' --with-bugurl=3Dhttps://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld Thread model: posix gcc version 9.3.0 (Rev2, Built by MSYS2 project)=