public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libstdc++/104748] New: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) @ 2022-03-01 15:39 redi at gcc dot gnu.org 2022-03-03 22:35 ` [Bug libstdc++/104748] " cvs-commit at gcc dot gnu.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: redi at gcc dot gnu.org @ 2022-03-01 15:39 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 Bug ID: 104748 Summary: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: testsuite-fail Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- With -D_GLIBCXX_DEBUG std::vector (aka std::__debug::vector) is not constexpr, so this test fails. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/104748] debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) 2022-03-01 15:39 [Bug libstdc++/104748] New: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) redi at gcc dot gnu.org @ 2022-03-03 22:35 ` cvs-commit at gcc dot gnu.org 2022-03-03 22:39 ` redi at gcc dot gnu.org 2024-02-08 12:43 ` redi at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: cvs-commit at gcc dot gnu.org @ 2022-03-03 22:35 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:5706a5db88a0eeaf82071debe1364f4533896a65 commit r12-7470-g5706a5db88a0eeaf82071debe1364f4533896a65 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 3 22:28:48 2022 +0000 libstdc++: Use non-debug vector in constexpr test [PR104748] The std::__debug::vector isn't usable in constant expressions, so this test fails in debug mode. Until the debug vector is fixed we can just make the test use the non-debug one. libstdc++-v3/ChangeLog: PR libstdc++/104748 * testsuite/std/ranges/adaptors/all.cc: Use non-debug vector for constexpr test. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/104748] debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) 2022-03-01 15:39 [Bug libstdc++/104748] New: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) redi at gcc dot gnu.org 2022-03-03 22:35 ` [Bug libstdc++/104748] " cvs-commit at gcc dot gnu.org @ 2022-03-03 22:39 ` redi at gcc dot gnu.org 2024-02-08 12:43 ` redi at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: redi at gcc dot gnu.org @ 2022-03-03 22:39 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-03-03 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- The test no longer FAILs, but we should still make the debug vector usable in constant expressions (by disabling its iterator tracking). ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/104748] debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) 2022-03-01 15:39 [Bug libstdc++/104748] New: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) redi at gcc dot gnu.org 2022-03-03 22:35 ` [Bug libstdc++/104748] " cvs-commit at gcc dot gnu.org 2022-03-03 22:39 ` redi at gcc dot gnu.org @ 2024-02-08 12:43 ` redi at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: redi at gcc dot gnu.org @ 2024-02-08 12:43 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Depends on| |109536 Target Milestone|--- |12.0 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #2) > The test no longer FAILs, but we should still make the debug vector usable > in constant expressions (by disabling its iterator tracking). That was done by r14-8252-g3d3145e9e1461e (and earlier related commits). Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109536 [Bug 109536] Failure to compile constexpr std::vector with -D_GLIBCXX_DEBUG ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-02-08 12:43 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-03-01 15:39 [Bug libstdc++/104748] New: debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors) redi at gcc dot gnu.org 2022-03-03 22:35 ` [Bug libstdc++/104748] " cvs-commit at gcc dot gnu.org 2022-03-03 22:39 ` redi at gcc dot gnu.org 2024-02-08 12:43 ` 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).