From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5406 invoked by alias); 17 Sep 2010 21:11:38 -0000 Received: (qmail 5366 invoked by uid 48); 17 Sep 2010 21:11:26 -0000 Date: Fri, 17 Sep 2010 21:11:00 -0000 Message-ID: <20100917211126.5365.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/45628] std::fstream::tellg invalidates I/O buffer In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "don dot wakefield at gmail dot com" 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: 2010-09/txt/msg02024.txt.bz2 ------- Comment #52 from don dot wakefield at gmail dot com 2010-09-17 21:11 ------- (In reply to comment #51) > ...As a matter of fact, many users found it also quite easy to > use, because - in case wasn't clear already from my previous comments - > **nobody ever** complained. I just have to butt in here. I don't expect any sympathy, but the only reason my company never complained about the performance issue with filebuf::seekoff(0,cur) is that we only just started using compilers which included that change. Our company can't be the only one beholden to conservative customers, so I won't be surprised if you get other questions similar to ours, years after the change went in. In any case, I appreciate all the effort you have put into this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45628