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++/52799] deque::emplace(iterator, ...) tries to call push_front(...), which doesn't exist Date: Mon, 18 Mar 2024 14:05:01 +0000 [thread overview] Message-ID: <bug-52799-4-gIoQgnvOPG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52799-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52799 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:1bb2bfb5d984456f59b42228f06d4ad4976358e7 commit r12-10240-g1bb2bfb5d984456f59b42228f06d4ad4976358e7 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jun 8 12:19:26 2023 +0100 libstdc++: Improve tests for emplace member of sequence containers Our existing tests for std::deque::emplace, std::list::emplace and std::vector::emplace are poor. We only have compile tests for PR 52799 and the equivalent for a const_iterator as the insertion point. This fails to check that the value is actually inserted correctly and the right iterator is returned. Add new tests that cover the existing 52799.cc and const_iterator.cc compile-only tests, as well as verifying the effects are correct. libstdc++-v3/ChangeLog: * testsuite/23_containers/deque/modifiers/emplace/52799.cc: Removed. * testsuite/23_containers/deque/modifiers/emplace/const_iterator.cc: Removed. * testsuite/23_containers/list/modifiers/emplace/52799.cc: Removed. * testsuite/23_containers/list/modifiers/emplace/const_iterator.cc: Removed. * testsuite/23_containers/vector/modifiers/emplace/52799.cc: Removed. * testsuite/23_containers/vector/modifiers/emplace/const_iterator.cc: Removed. * testsuite/23_containers/deque/modifiers/emplace/1.cc: New test. * testsuite/23_containers/list/modifiers/emplace/1.cc: New test. * testsuite/23_containers/vector/modifiers/emplace/1.cc: New test. (cherry picked from commit 3ec1d76a359542ed4c8370390efa9ee9e25e757f)
prev parent reply other threads:[~2024-03-18 14:05 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-30 23:18 [Bug libstdc++/52799] New: " jyasskin at gcc dot gnu.org 2012-03-31 1:27 ` [Bug libstdc++/52799] " paolo.carlini at oracle dot com 2012-03-31 1:57 ` paolo at gcc dot gnu.org 2012-03-31 1:59 ` paolo at gcc dot gnu.org 2012-03-31 2:03 ` paolo.carlini at oracle dot com 2023-06-09 8:55 ` cvs-commit at gcc dot gnu.org 2023-06-29 23:00 ` cvs-commit at gcc dot gnu.org 2024-03-18 14:05 ` cvs-commit at gcc dot gnu.org [this message]
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-52799-4-gIoQgnvOPG@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).