public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/7076: iostreams very slow compared with earlier gcc versions Date: Fri, 07 Feb 2003 02:56:00 -0000 [thread overview] Message-ID: <20030207025600.22418.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/7076; it has been noted by GNATS. From: Joe Buck <jbuck@synopsys.com> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, morten@wtf.dk Cc: Subject: Re: libstdc++/7076: iostreams very slow compared with earlier gcc versions Date: Thu, 06 Feb 2003 18:48:06 -0800 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7076 It seems that snprintf is being called now, while it wasn't in libstdc++ version 2, making things about 8x to more than 20x slower depending on details.
next reply other threads:[~2003-02-07 2:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-07 2:56 Joe Buck [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-20 18:28 bkoz 2002-06-19 6:26 morten
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=20030207025600.22418.qmail@sources.redhat.com \ --to=jbuck@synopsys.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).