public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/4150: catastrophic performance decrease in C++ code
Date: Mon, 15 Apr 2002 16:16:00 -0000	[thread overview]
Message-ID: <20020415231603.10908.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/4150; it has been noted by GNATS.

From: Jason Merrill <jason@redhat.com>
To: libstdc++@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/4150: catastrophic performance decrease in C++ code
Date: Tue, 16 Apr 2002 00:15:10 +0100

 >>>>> "Jason" == Jason Merrill <jason@redhat.com> writes:
 
 > is there any reason why we can't leave the file pointer at the end of the
 > last read block, rather than at the beginning as we do now?
 
 Which is what libio does, and which would seem to be the only way to avoid
 this sort of problem.  Can anyone enlighten me as to the design
 goals/decisions of the current implementation?
 
 Continuing to hack...
 
 Jason


             reply	other threads:[~2002-04-15 23:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 16:16 Jason Merrill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23  5:23 jason
2002-04-18  4:06 Jason Merrill
2002-04-18  3:06 Jason Merrill
2002-04-17 21:56 Benjamin Kosnik
2002-04-17 19:26 Jason Merrill
2002-04-16  5:46 Jason Merrill
2002-04-15  7:42 jason
2002-04-14 19:36 Jason Merrill
2002-04-14 11:13 jason
2002-04-11 18:20 ljrittle
2002-04-11 17:19 rth

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=20020415231603.10908.qmail@sources.redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@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).