public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/112491] std::deque<T,Allocator>::size xmethod output is wrong
Date: Wed, 15 Nov 2023 10:04:28 +0000 [thread overview]
Message-ID: <bug-112491-4-U5Ycn1WHQb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112491-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112491
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> The bug occurs when the first node of the deque is not filled from the first
> element. That case was never tested.
The deque::operator[] xmethod is wrong in the same scenarios.
next prev parent reply other threads:[~2023-11-15 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 12:21 [Bug libstdc++/112491] New: " ks1322 at gmail dot com
2023-11-14 8:22 ` [Bug libstdc++/112491] " redi at gcc dot gnu.org
2023-11-14 14:56 ` redi at gcc dot gnu.org
2023-11-14 15:13 ` redi at gcc dot gnu.org
2023-11-14 15:58 ` cvs-commit at gcc dot gnu.org
2023-11-14 22:40 ` cvs-commit at gcc dot gnu.org
2023-11-14 22:43 ` cvs-commit at gcc dot gnu.org
2023-11-14 23:11 ` cvs-commit at gcc dot gnu.org
2023-11-14 23:12 ` redi at gcc dot gnu.org
2023-11-15 10:04 ` redi at gcc dot gnu.org [this message]
2023-11-15 11:28 ` cvs-commit at gcc dot gnu.org
2023-11-15 11:33 ` cvs-commit at gcc dot gnu.org
2023-11-15 11:35 ` cvs-commit at gcc dot gnu.org
2023-11-15 11:42 ` cvs-commit at gcc dot gnu.org
2023-11-15 11:44 ` 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-112491-4-U5Ycn1WHQb@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).