From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6790E3858C5F; Sat, 4 Feb 2023 03:04:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6790E3858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675479868; bh=xyazjzWMQTGfOSDquVst0RcQsh/+2i4BQ97vOel8uDc=; h=From:To:Subject:Date:From; b=P6xee0v1PVkgIZ22wpy1pE32vCr+i9+w8yp6mNIB39AvG/sE65kIVRHroghA7SwEY 3b0b/vLvWSMBdqedIU247r9fNNWmrlAgP1qPBX5MgA7F5kMyxKEzwa8WPVIe2tf45J /Cv1QU3/XHgXgZ1spLxDYv8ITsq4jMiGl5lioaRc= From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108672] New: [13 Regression] g++.dg/modules/xtreme-header-2_a.H, _b.C, _c.C Date: Sat, 04 Feb 2023 03:04:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 13.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 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=3D108672 Bug ID: 108672 Summary: [13 Regression] g++.dg/modules/xtreme-header-2_a.H, _b.C, _c.C Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org Target Milestone: --- Target: cris-elf, pru-elf Tl;DR: not a dup of PR98531, but a bug in libstdc++-v3. Also, a regression. For cris-elf, these failures appeared with a commit in the range r13-2740-gd812e8cb2a920f..r13-2748-g59f6dea963b5f7: Build log: Running /x/gcc/testsuite/g++.dg/modules/modules.exp ... <...removing non-regression FAILs...> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=3Dc++17 (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi=20 (gcm.cache/$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=3Dc++17 (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=3Dc++17 (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=3Dc++2a (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi=20 (gcm.cache/$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=3Dc++2a (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=3Dc++2a (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=3Dc++2b (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi=20 (gcm.cache/$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=3Dc++2b (test for excess erro= rs) FAIL: g++.dg/modules/xtreme-header-2_c.C -std=3Dc++2b (test for excess erro= rs) They don't appear for {s390x, powerpc64, i686, x86_64, aarch64, arm}-linux-= gnu. They're there for pru-elf where the context looks the same as for cris-elf: (https://gcc.gnu.org/pipermail/gcc-testresults/2023-January/775193.html). The commit exposing the failure appears to be r13-2745-gc77f556741ded4, "c+= +: xtreme-header modules tests cleanups", due to the '+#include '. In g++.log for cris-elf, we can see that they all fail either fail similarly as follows: In file included from /x/gcc/libstdc++-v3/include/pstl/memory_impl.h:15, from /x/gcc/libstdc++-v3/include/pstl/algorithm_impl.h:20, from /x/gccobj/cris-elf/libstdc++-v3/include/pstl/glue_execution_defs.h:50, from /x/gccobj/cris-elf/libstdc++-v3/include/execution:34, from /x/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2.h= :4, from /x/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H:4: /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h: In function 'bool __pstl::__unseq_backend::__simd_or(_Index, _Di\ fferenceType, _Pred)': /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:77:9: error: 'int32_t' was not declared in this scope /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:77:9: note: 'int32_t'= is defined in header ''; did you f\ orget to '#include '? /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:81:17: error: '__flag' was not declared in this scope /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:82:14: error: '__flag' was not declared in this scope /x/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: At global scope: /x/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: warning: not writi= ng module '/x/gcc/gcc/testsuite/g++.dg/modul\ es/xtreme-header-2_a.H' due to errors compiler exited with status 1 FAIL: g++.dg/modules/xtreme-header-2_a.H -std=3Dc++17 (test for excess erro= rs) Excess errors: /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:77:9: error: 'int32_t' was not declared in this scope /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:81:17: error: '__flag' was not declared in this scope /x/gcc/libstdc++-v3/include/pstl/unseq_backend_simd.h:82:14: error: '__flag' was not declared in this scope /x/gcc/gcc/testsuite/g++.dg/modules/xtreme-header-2_a.H: warning: not writi= ng module '/x/gcc/gcc/testsuite/g++.dg/modul\ es/xtreme-header-2_a.H' due to errors FAIL: g++.dg/modules/xtreme-header-2_a.H module-cmi=20 (gcm.cache/$srcdir/g++.dg/modules/xtreme-header-2_a.H.gcm) The error for cris-elf seems to be a "naked" use of int32_t; not having a fitting #include: stdint.h or cstdint or inttypes.h or whatever, for use in libstdc++-v3/include/pstl/unseq_backend_simd.h. This is not exposed on e.g. native x86_64-pc-linux-gnu, because there, it's included as an effect of including stdlib.h in cstdlib (follow the trace in xtreme-header-2_a.ii with glibc-2.31-13+deb11u5). Will submit patch shortl= y.=