public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/23767] std::vector iterator implementation wrong
Date: Wed, 07 Sep 2005 20:45:00 -0000 [thread overview]
Message-ID: <20050907204507.11548.qmail@sourceware.org> (raw)
In-Reply-To: <20050907170304.23767.afra@cs.stanford.edu>
------- Additional Comments From pcarlini at suse dot de 2005-09-07 20:45 -------
(In reply to comment #9)
> Actually, __normal_iterator is what std::string uses for it's iterator class,
> so we could be in trouble.
As long as no user code expects instantiations of members of __normal_iterator
inside the library proper to link against I don't think there are any risks (At
least, this is my present understanding of these torny matters)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23767
next prev parent reply other threads:[~2005-09-07 20:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 17:03 [Bug c++/23767] New: " afra at cs dot stanford dot edu
2005-09-07 17:04 ` [Bug c++/23767] " afra at cs dot stanford dot edu
2005-09-07 17:06 ` [Bug libstdc++/23767] " afra at cs dot stanford dot edu
2005-09-07 17:13 ` pinskia at gcc dot gnu dot org
2005-09-07 19:22 ` chris at bubblescope dot net
2005-09-07 19:22 ` chris at bubblescope dot net
2005-09-07 19:33 ` pcarlini at suse dot de
2005-09-07 19:37 ` pcarlini at suse dot de
2005-09-07 19:40 ` pcarlini at suse dot de
2005-09-07 20:07 ` chris at bubblescope dot net
2005-09-07 20:14 ` pcarlini at suse dot de
2005-09-07 20:19 ` bangerth at dealii dot org
2005-09-07 20:27 ` pcarlini at suse dot de
2005-09-07 20:40 ` chris at bubblescope dot net
2005-09-07 20:45 ` pcarlini at suse dot de [this message]
2005-09-07 20:51 ` chris at bubblescope dot net
2005-09-07 20:55 ` bangerth at dealii dot org
2005-09-07 20:58 ` pcarlini at suse dot de
2005-09-07 21:04 ` pcarlini at suse dot de
2005-09-07 21:07 ` chris at bubblescope dot net
2005-09-07 21:27 ` bangerth at dealii dot org
2005-09-07 21:36 ` pcarlini at suse dot de
2005-09-07 22:40 ` bangerth at dealii dot org
2005-09-08 3:36 ` fang at csl dot cornell dot edu
2005-09-11 14:32 ` pcarlini at suse dot de
2005-09-12 9:44 ` cvs-commit at gcc dot gnu dot org
2005-09-12 9:46 ` pcarlini at suse dot de
2005-09-12 9:46 ` pcarlini at suse dot de
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=20050907204507.11548.qmail@sourceware.org \
--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).