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++/104858] ranges::minmax double dereferences first
Date: Fri, 15 Apr 2022 18:42:07 +0000 [thread overview]
Message-ID: <bug-104858-4-6kJGM6fJvy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104858-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104858
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:7e76cef873342a66408c126abceaf7dbddd3f477
commit r12-8178-g7e76cef873342a66408c126abceaf7dbddd3f477
Author: Patrick Palka <ppalka@redhat.com>
Date: Fri Apr 15 14:41:14 2022 -0400
libstdc++: Avoid double-deref of __first in ranges::minmax [PR104858]
PR libstdc++/104858
libstdc++-v3/ChangeLog:
* include/bits/ranges_algo.h (__minmax_fn): Avoid dereferencing
__first twice at the start.
* testsuite/25_algorithms/minmax/constrained.cc (test06): New test.
next prev parent reply other threads:[~2022-04-15 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:01 [Bug libstdc++/104858] New: " barry.revzin at gmail dot com
2022-03-10 9:38 ` [Bug libstdc++/104858] " redi at gcc dot gnu.org
2022-03-10 15:37 ` ppalka at gcc dot gnu.org
2022-04-15 18:42 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-15 18:44 ` ppalka at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 9:58 ` rguenth 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-104858-4-6kJGM6fJvy@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: link
Be 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).