public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	peturr02@ru.is
Subject: Re: libstdc++/9876: filebuf::sputc more than 10% slower than putc
Date: Thu, 27 Feb 2003 20:22:00 -0000	[thread overview]
Message-ID: <20030227202205.32613.qmail@sources.redhat.com> (raw)

Synopsis: filebuf::sputc more than 10% slower than putc

State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Thu Feb 27 20:22:05 2003
State-Changed-Why:
    Yes, filebuf::sputc shall be improved: patches welcome,
    or, otherwise, stay tuned!
    
    However, the funny thing of your PR is that, as a matter of
    fact, I *cannot* reproduce the trend neither with mainline
    (which produces better code, indeed) nor with 3.2.2!
    
    On my P4-2400 (512 MB, linux2.4.20, glibc2.3.1, etc.),
    these are the timings (gcc-3.2.2, -O2):
    iostreams:
     3.500u 0.330s 0:03.92 97.7%     0+0k 0+0io 197pf+0w
    stdio:
     3.570u 0.430s 0:04.03 99.2%     0+0k 0+0io 194pf+0w
    
    Ideas?
    
    Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9876


             reply	other threads:[~2003-02-27 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 20:22 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16 18:06 Benjamin Kosnik
2003-05-16 17:56 Paolo Carlini
2003-03-23 19:46 Pétur Runólfsson
2003-03-03 11:16 Pétur Runólfsson
2003-02-28 16:46 Paolo Carlini
2003-02-28 16:06 Pétur Runólfsson
2003-02-27 10:36 peturr02

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=20030227202205.32613.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=peturr02@ru.is \
    /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).