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++/17140] Floating point output is slow Date: Sun, 21 Nov 2004 23:39:00 -0000 [thread overview] Message-ID: <20041121233937.21913.qmail@sourceware.org> (raw) In-Reply-To: <20040823040835.17140.jlquinn@gcc.gnu.org> ------- Additional Comments From pcarlini at suse dot de 2004-11-21 23:39 ------- Hi again. As expected, fpfinal3 regtests Ok on x86/x86_64/ia64-linux. I'm attaching what I have actually tested: doesn't include the regenerated files and avoids a warning about the unused __mod argument of _M_insert_float. Tomorrow, would like to run on the 64-bit machines the specific floating point output tests. A final note: we should add a testcase for the fixed (corner case) issue with grouping (which, basically, is a WONTFIX for 3.3 and 3.4) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17140
next prev parent reply other threads:[~2004-11-21 23:39 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-23 4:08 [Bug libstdc++/17140] New: " jlquinn at gcc dot gnu dot org 2004-08-23 5:31 ` [Bug libstdc++/17140] " pinskia at gcc dot gnu dot org 2004-09-02 18:05 ` bkoz at gcc dot gnu dot org 2004-09-03 12:46 ` jlquinn at gcc dot gnu dot org 2004-09-03 15:00 ` bkoz at gcc dot gnu dot org 2004-09-03 15:57 ` bkoz at gcc dot gnu dot org 2004-09-04 15:21 ` jlquinn at gcc dot gnu dot org 2004-09-07 13:51 ` pcarlini at suse dot de 2004-11-15 15:02 ` jlquinn at gcc dot gnu dot org 2004-11-15 17:04 ` bkoz at redhat dot com 2004-11-15 17:24 ` jlquinn at gcc dot gnu dot org 2004-11-17 4:40 ` jlquinn at gcc dot gnu dot org 2004-11-19 22:34 ` bkoz at gcc dot gnu dot org 2004-11-19 22:34 ` pcarlini at suse dot de 2004-11-21 23:39 ` pcarlini at suse dot de [this message] 2004-11-22 9:44 ` pcarlini at suse dot de 2004-11-22 9:58 ` pcarlini at suse dot de 2004-11-22 10:37 ` pcarlini at suse dot de 2004-11-22 18:14 ` pcarlini at suse dot de 2004-12-16 4:43 ` jlquinn at gcc dot gnu dot org 2004-12-20 21:01 ` jlquinn at gcc dot gnu dot org 2004-12-21 19:19 ` jlquinn at gcc dot gnu dot org 2004-12-21 19:40 ` jlquinn at gcc dot gnu dot org 2004-12-21 19:43 ` pinskia at gcc dot gnu dot org 2004-12-21 19:45 ` pinskia at gcc dot gnu dot org 2004-12-21 20:39 ` pcarlini at suse dot de 2005-01-03 14:58 ` pcarlini at suse dot de 2005-01-03 15:27 ` pcarlini at suse dot de 2005-01-03 16:41 ` pcarlini at suse dot de 2005-01-03 22:05 ` jlquinn at gcc dot gnu dot org 2005-01-16 17:09 ` jlquinn at optonline dot net 2005-01-16 17:13 ` pcarlini at suse dot de 2005-01-26 14:34 ` pinskia at gcc dot gnu dot org
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=20041121233937.21913.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: 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).