public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/19642] streaming doubles is very slow compared to sprintf
Date: Wed, 26 Jan 2005 15:45:00 -0000 [thread overview]
Message-ID: <20050126154531.13843.qmail@sourceware.org> (raw)
In-Reply-To: <20050126142651.19642.joerg.richter@pdv-fs.de>
------- Additional Comments From pcarlini at suse dot de 2005-01-26 15:45 -------
> Doesn't a function that is on 99% of all call stacks automatically consume 99%
> of the runtime? Ok, the time can also be spend in the childs like here in
> __issetuid, but this is an implementation detail of setlocale, isn't it?
% in *time*, see the linux example, nothing special.
Ok about snprintf, it's not that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19642
next prev parent reply other threads:[~2005-01-26 15:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 14:27 [Bug c++/19642] New: " joerg dot richter at pdv-fs dot de
2005-01-26 14:27 ` [Bug libstdc++/19642] " pinskia at gcc dot gnu dot org
2005-01-26 14:34 ` pinskia at gcc dot gnu dot org
2005-01-26 14:47 ` pcarlini at suse dot de
2005-01-26 14:56 ` pcarlini at suse dot de
2005-01-26 15:00 ` joerg dot richter at pdv-fs dot de
2005-01-26 15:10 ` pcarlini at suse dot de
2005-01-26 15:18 ` joerg dot richter at pdv-fs dot de
2005-01-26 15:22 ` pcarlini at suse dot de
2005-01-26 15:37 ` pcarlini at suse dot de
2005-01-26 15:41 ` joerg dot richter at pdv-fs dot de
2005-01-26 15:45 ` pcarlini at suse dot de [this message]
2005-01-26 16:00 ` joerg dot richter at pdv-fs dot de
2005-01-26 16:17 ` pcarlini at suse dot de
2005-01-26 17:34 ` pcarlini at suse dot de
2005-01-26 17:34 ` pcarlini at suse dot de
2005-01-26 19:31 ` dje at gcc dot gnu dot org
2005-01-27 8:09 ` joerg dot richter at pdv-fs dot de
2005-01-27 11:12 ` pcarlini at suse dot de
2005-01-27 12:25 ` pcarlini at suse dot de
2005-01-27 12:33 ` pcarlini at suse dot de
2005-01-27 12:40 ` joerg dot richter at pdv-fs dot de
2005-01-27 12:47 ` pcarlini at suse dot de
2005-01-27 12:54 ` joerg dot richter at pdv-fs dot de
2005-01-27 12:58 ` pcarlini at suse dot de
2005-01-27 15:05 ` joerg dot richter at pdv-fs dot de
2005-01-27 15:59 ` pcarlini at suse dot de
2005-01-27 16:39 ` bkoz at gcc dot gnu dot org
2005-01-27 16:57 ` pcarlini at suse dot de
2005-01-28 7:54 ` joerg dot richter at pdv-fs dot de
2005-01-28 9:58 ` pcarlini at suse dot de
2005-01-30 14:10 ` cvs-commit at gcc dot gnu dot org
2005-02-02 15:43 ` pcarlini at suse dot de
2005-02-02 16:47 ` cvs-commit at gcc dot gnu dot org
2005-02-02 16:48 ` pcarlini at suse dot de
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=20050126154531.13843.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).