public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106320] [10 regression] build failure (due to view requirement changes?) Date: Mon, 12 Sep 2022 19:21:41 +0000 [thread overview] Message-ID: <bug-106320-4-bzk9CGKVsk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106320-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106320 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:f323610375f4f87098f98b501ab01d033c930558 commit r12-8757-gf323610375f4f87098f98b501ab01d033c930558 Author: Patrick Palka <ppalka@redhat.com> Date: Mon Sep 12 15:05:04 2022 -0400 libstdc++: Add already-accepted <ranges> testcase [PR106320] Although PR106320 affected only the 10 and 11 branches, and the testcase from there is already correctly accepted on trunk and the 12 branch, we still should add the testcase to trunk/12 too for inter-branch consistency. PR libstdc++/106320 libstdc++-v3/ChangeLog: * testsuite/std/ranges/adaptors/join.cc (test13): New test. (cherry picked from commit db19cfdac8ede93172aecc58612171c239c993ad)
next prev parent reply other threads:[~2022-09-12 19:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-15 21:03 [Bug c++/106320] New: " h2+bugs at fsfe dot org 2022-07-18 7:40 ` [Bug libstdc++/106320] " rguenth at gcc dot gnu.org 2022-07-18 9:02 ` redi at gcc dot gnu.org 2022-07-18 9:30 ` marxin at gcc dot gnu.org 2022-07-18 10:35 ` redi at gcc dot gnu.org 2022-07-18 13:25 ` ppalka at gcc dot gnu.org 2022-07-22 16:53 ` cvs-commit at gcc dot gnu.org 2022-07-22 17:06 ` cvs-commit at gcc dot gnu.org 2022-07-22 17:49 ` h2+bugs at fsfe dot org 2022-09-12 19:05 ` cvs-commit at gcc dot gnu.org 2022-09-12 19:21 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-12 19:23 ` ppalka at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-106320-4-bzk9CGKVsk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).