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++/115119] Typo in _Grapheme_cluster_view::_Iterator::operator++(int)
Date: Fri, 17 May 2024 13:17:50 +0000	[thread overview]
Message-ID: <bug-115119-4-OBvaKezClb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115119-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115119

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:e909d360dfaeafa9f45eda2461a1bedffac99ac2

commit r14-10215-ge909d360dfaeafa9f45eda2461a1bedffac99ac2
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu May 16 17:15:55 2024 +0100

    libstdc++: Fix typo in _Grapheme_cluster_view::_Iterator [PR115119]

    libstdc++-v3/ChangeLog:

            PR libstdc++/115119
            * include/bits/unicode.h (_Iterator::operator++(int)): Fix typo
            in increment expression.
            * testsuite/ext/unicode/grapheme_view.cc: Check post-increment
            on view's iterator.

    (cherry picked from commit c9e05b03c18e898be604ab90401476e9c473cc52)

  parent reply	other threads:[~2024-05-17 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 15:43 [Bug libstdc++/115119] New: " davidfromonline at gmail dot com
2024-05-16 15:46 ` [Bug libstdc++/115119] " pinskia at gcc dot gnu.org
2024-05-16 15:56 ` redi at gcc dot gnu.org
2024-05-16 16:00 ` redi at gcc dot gnu.org
2024-05-16 16:20 ` redi at gcc dot gnu.org
2024-05-16 18:26 ` jakub at gcc dot gnu.org
2024-05-17 12:43 ` redi at gcc dot gnu.org
2024-05-17 12:47 ` cvs-commit at gcc dot gnu.org
2024-05-17 13:17 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-17 13:19 ` 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-115119-4-OBvaKezClb@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).