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++/110990] `format_to_n` returns wrong value
Date: Mon, 14 Aug 2023 17:48:33 +0000	[thread overview]
Message-ID: <bug-110990-4-n2eaDwKE1V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110990-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:8f82863df33c63693a355d9244c315ef5cb2158e

commit r13-7721-g8f82863df33c63693a355d9244c315ef5cb2158e
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Aug 11 23:02:44 2023 +0100

    libstdc++: Fix std::format_to_n return value [PR110990]

    When writing to a contiguous iterator, std::format_to_n(out, n, ...)
    always returns out + n, even if it wrote fewer than n characters to the
    iterator.

    The problem is in the _M_finish() member function of the _Iter_sink
    specialization for contiguous iterators. _M_finish() calls _M_overflow()
    to update its count of characters written, so it can return the count of
    characters that would be written if there was room. But _M_overflow()
    assumes it's only called when the buffer is full, and so switches to the
    internal buffer. _M_finish() then thinks that if the internal buffer is
    in use, we already wrote at least n characters and so returns out+n as
    the output position.

    We can fix the problem by adding a check in _M_overflow() so that we
    don't update the count and switch to the internal buffer unless we've
    run out of room, i.e. _M_unused().size() is zero. The caller then needs
    to be prepared for _M_count not being the final total, and so add
    _M_used.size() to it.

    However, there's not actually any need for _M_finish() to call
    _M_overflow() to get the count. We now need to use _M_count and
    _M_used.size() to get the total anyway so _M_overflow() doesn't help
    with that. And we don't need to use _M_overflow() to flush unwritten
    characters to the output, because the specialization for contiguous
    iterators always writes directly to the output without buffering (except
    when we've exceeded the maximum number of characters, in which case we
    want to discard the buffered characters anyway). So _M_finish() can be
    simplified and can avoid calling _M_overflow().

    This change also fixes some member functions of other sink classes to
    only call _M_overflow() when there are characters in the buffer, which
    is needed to meet _M_overflow's precondition that _M_used().size()!=0.

    libstdc++-v3/ChangeLog:

            PR libstdc++/110990
            * include/std/format (_Seq_sink::get): Only call _M_overflow if
            its precondition is met.
            (_Iter_sink::_M_finish): Likewise.
            (_Iter_sink<C, ContigIter>::_M_overflow): Only switch to the
            internal buffer after running out of space.
            (_Iter_sink<C, ContigIter>::_M_finish): Do not use _M_overflow.
            (_Counting_sink::count): Likewise.
            * testsuite/std/format/functions/format_to_n.cc: Check cases
            where the output fits into the buffer.

    (cherry picked from commit 003016a40844701c48851020df672b70f3446bdb)

  parent reply	other threads:[~2023-08-14 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 10:55 [Bug libstdc++/110990] New: " ensadc at mailnesia dot com
2023-08-11 17:17 ` [Bug libstdc++/110990] " redi at gcc dot gnu.org
2023-08-11 21:58 ` redi at gcc dot gnu.org
2023-08-11 22:34 ` cvs-commit at gcc dot gnu.org
2023-08-11 22:36 ` redi at gcc dot gnu.org
2023-08-14 17:48 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-14 17:51 ` 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-110990-4-n2eaDwKE1V@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).