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++/103853] std::forward_list::merge should check if __list != this Date: Thu, 21 Apr 2022 12:33:15 +0000 [thread overview] Message-ID: <bug-103853-4-4eYStNuRmP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103853-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103853 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:2089886d5743c20ce0b41d68f0a4cbe097b46704 commit r11-9909-g2089886d5743c20ce0b41d68f0a4cbe097b46704 Author: Pavel I. Kryukov <pavel.kryukov@phystech.edu> Date: Thu Jan 6 12:32:36 2022 +0000 libstdc++: Add self-merge check to std::forward_list::merge [PR103853] This implements the proposed resolution of LWG 3088, so that x.merge(x) is a no-op, consistent with std::list::merge. Signed-off-by: Pavel I. Kryukov <pavel.kryukov@phystech.edu> Co-authored-by: Jonathan Wakely <jwakely@redhat.com> libstdc++-v3/ChangeLog: PR libstdc++/103853 * include/bits/forward_list.tcc (forward_list::merge): Check for self-merge. * testsuite/23_containers/forward_list/operations/merge.cc: New test. (cherry picked from commit 52ebc2be0990d6d3a46bb716164f9cef6f661021)
next prev parent reply other threads:[~2022-04-21 12:33 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-28 20:43 [Bug libstdc++/103853] New: " pavel.kryukov at phystech dot edu 2021-12-29 10:12 ` [Bug libstdc++/103853] " redi at gcc dot gnu.org 2021-12-29 10:22 ` redi at gcc dot gnu.org 2022-01-05 10:06 ` redi at gcc dot gnu.org 2022-01-05 10:48 ` redi at gcc dot gnu.org 2022-01-05 14:40 ` pavel.kryukov at phystech dot edu 2022-01-05 14:47 ` redi at gcc dot gnu.org 2022-01-06 10:50 ` pavel.kryukov at phystech dot edu 2022-01-06 15:00 ` cvs-commit at gcc dot gnu.org 2022-01-06 15:39 ` redi at gcc dot gnu.org 2022-01-06 19:02 ` pavel.kryukov at phystech dot edu 2022-04-21 12:33 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-26 13:11 ` cvs-commit at gcc dot gnu.org 2022-05-09 16:40 ` cvs-commit at gcc dot gnu.org 2022-05-09 19:45 ` redi 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-103853-4-4eYStNuRmP@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).