From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28981 invoked by alias); 12 Apr 2002 01:20:07 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28945 invoked by uid 61); 12 Apr 2002 01:20:06 -0000 Date: Thu, 11 Apr 2002 18:20:00 -0000 Message-ID: <20020412012006.28944.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, leitner@fefe.de, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, leitner@fefe.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/4150: catastrophic performance decrease in C++ code X-SW-Source: 2002-04/txt/msg00638.txt.bz2 List-Id: Synopsis: catastrophic performance decrease in C++ code State-Changed-From-To: analyzed->feedback State-Changed-By: ljrittle State-Changed-When: Thu Apr 11 18:20:06 2002 State-Changed-Why: The root issue here is related to PR/5820. If someone on a Linux platform could *please* just try my suggested fix (which is already used on platforms where it is not legal to seek on interactive streams), then this whole seeking performance problem will go away entirely for you... See concurrent post to libstdc++ mailing list. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4150