From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 89BFE3858C2D; Mon, 27 Nov 2023 23:09:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89BFE3858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701126586; bh=ifMfdsnE+0b07Oc/aGQZ1PhbKNeNZs84PDTxh4laLv4=; h=From:To:Subject:Date:From; b=QPxTcjTtQyKfT4vdFwG2siMksAdlPrayDkRJ1AgLphZ1RdnxUrj1JKw/efykwJOea tVixzrKOvWXnyBb01D1KB91AD93XZ5DBaBXbvq0RFo0vTnCBrt/+T+/YhnFxDFOijP FsvPsCZ6bO0hM/SJWTrshnGOM5+vT0uO+sqINtUs= From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112737] New: [14 Regression] g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors) Date: Mon, 27 Nov 2023 23:09:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget Message-ID: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112737 Bug ID: 112737 Summary: [14 Regression] g++.dg/modules/xtreme-header-2_b.C -std=3Dc++2b (test for excess errors) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org CC: redi at gcc dot gnu.org Target Milestone: --- Target: cris-elf With r14-5794-g7a6a29c455e775 "libstdc++: Define std::ranges::to for C++23 (P1206R7) [PR111055]" this test-suite regression was introduced for various targets: Running /x/gcc/testsuite/g++.dg/modules/modules.exp ... [...] FAIL: g++.dg/modules/xtreme-header-2_b.C -std=3Dc++2b (test for excess erro= rs) According to g++.log, for cris-elf: Excess errors: /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'template class _Cont, class = _Rg, class ... _Args> using std::ranges::__detail::_DeduceExpr1 =3D decltype (_Cont<...auto...>(declval<_Rg>(), (declval<_Args>)()...))' /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'template class _Cont, class = _Rg, class ... _Args> using std::ranges::__detail::_DeduceExpr2 =3D decltype (_Cont<...auto...>(std::from_range, declval<_Rg>(), (declval<_Args>)()...))' /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'template class _Cont, class = _Rg, class ... _Args> using std::ranges::__detail::_DeduceExpr3 =3D decltype (_Cont<...auto...>(declval >(), declval >(), (declval<_Args>)()...))' /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'using std::ranges::__detail::_DeduceExpr1 =3D de= cltype (_Cont<...auto...>(declval<_Rg>(), (declval<_Args>)()...))' /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'using std::ranges::__detail::_DeduceExpr2 =3D de= cltype (_Cont<...auto...>(std::from_range, declval<_Rg>(), (declval<_Args>)()...))' /src/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: error: conflicting global module declaration 'using std::ranges::__detail::_DeduceExpr3 =3D de= cltype (_Cont<...auto...>(declval >(), declval >(), (declval<_Args>)()...))' This appears to happen also for "aarch64": https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078616.html and "Linux/x86_64": https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078617.html suggesting that most targets are affected. (Maintainers, please adjust your scripts to include a full gnu target tuple= in your autotester messages in those places where the abbreviated quoted ones = are found, so that readers can cut-and-paste that key information for e.g. additional targets in bug-reports, QED. Additional steps such as following links should not be necessary.)=