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++/66742] abort on sorting list with custom allocator that is not stateless Date: Wed, 03 Nov 2021 16:51:30 +0000 [thread overview] Message-ID: <bug-66742-4-etwUX9uawT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66742-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66742 --- Comment #19 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:1e7a269856fd67aff78ac874bec96d31a54b2fd9 commit r12-4873-g1e7a269856fd67aff78ac874bec96d31a54b2fd9 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 2 10:21:01 2021 +0000 libstdc++: Fix regression in std::list::sort [PR66742] The standard does not require const-correct comparisons in list::sort. libstdc++-v3/ChangeLog: PR libstdc++/66742 * include/bits/list.tcc (list::sort): Use mutable iterators for comparisons. * include/bits/stl_list.h (_Scratch_list::_Ptr_cmp): Likewise. * testsuite/23_containers/list/operations/66742.cc: Check non-const comparisons.
next prev parent reply other threads:[~2021-11-03 16:51 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-02 14:46 [Bug libstdc++/66742] New: abort on sorting list with custom compiler " mdiluzio at feralinteractive dot com 2015-07-02 19:40 ` [Bug libstdc++/66742] " daniel.kruegler at googlemail dot com 2015-07-02 20:47 ` redi at gcc dot gnu.org 2015-07-03 8:14 ` mdiluzio at feralinteractive dot com 2015-07-03 8:20 ` mdiluzio at feralinteractive dot com 2015-07-03 10:20 ` redi at gcc dot gnu.org 2015-07-03 10:29 ` redi at gcc dot gnu.org 2021-04-10 0:53 ` [Bug libstdc++/66742] abort on sorting list with custom allocator " ahuszagh at gmail dot com 2021-04-19 10:40 ` redi at gcc dot gnu.org 2021-04-27 11:37 ` jakub at gcc dot gnu.org 2021-05-25 20:52 ` redi at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2021-10-01 19:40 ` cvs-commit at gcc dot gnu.org 2021-10-01 19:56 ` redi at gcc dot gnu.org 2021-11-02 10:16 ` redi at gcc dot gnu.org 2021-11-03 16:51 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-06 8:29 ` jakub at gcc dot gnu.org 2022-05-06 12:30 ` 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-66742-4-etwUX9uawT@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).