From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29694 invoked by alias); 5 Sep 2011 10:00:05 -0000 Received: (qmail 29511 invoked by uid 22791); 5 Sep 2011 10:00:01 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Sep 2011 09:59:15 +0000 From: "marc.glisse at normalesup dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/46906] istreambuf_iterator is late? Date: Mon, 05 Sep 2011 10:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marc.glisse at normalesup dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg00301.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46906 --- Comment #5 from Marc Glisse 2011-09-05 09:58:19 UTC --- (In reply to comment #4) > IMO the example program is broken and cannot be used to proof violation of > contract of the library. This is so, because istreambuf_iterator is an input > iterator and any usage of operator++ potentially invalidates copies of the > iterator (see FDIS, Table 107, expression r++). You are completely right, thanks. On the other hand, it looks like I can construct i2 from s (instead of copying from i1) and still hit the same issue with a valid program. Do you agree? (Hmm, could the standard make it undefined to interlace uses of an istreambuf_iterator and other operations on the istreambuf, to allow this behavior?)