public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19974] incorrect complex division on ia-64 with flag_complex_method = 2
Date: Thu, 17 Feb 2005 03:45:00 -0000 [thread overview]
Message-ID: <20050216205110.5596.qmail@sourceware.org> (raw)
In-Reply-To: <20050215161817.19974.Thomas.Koenig@online.de>
------- Additional Comments From Thomas dot Koenig at online dot de 2005-02-16 20:51 -------
Checking this on i686-unknown-linux-gnu, I find the same
result with flag_complex_method=2 as on ia-64. I am also
seeing the same result with logarithmic scaling (using frexp and
ldexp). Maybe I'm being bitten by the decimal fractions not being exactly
representable in binary, and the Lapack failure has some other reason.
I'll keep looking.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19974
next prev parent reply other threads:[~2005-02-16 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 21:20 [Bug middle-end/19974] New: Lapack hang in xeigtstc on ia-64 Thomas dot Koenig at online dot de
2005-02-15 21:28 ` [Bug middle-end/19974] " Thomas dot Koenig at online dot de
2005-02-15 21:43 ` Thomas dot Koenig at online dot de
2005-02-15 23:18 ` Thomas dot Koenig at online dot de
2005-02-16 17:27 ` [Bug middle-end/19974] incorrect complex division on ia-64 with flag_complex_method = 2 Thomas dot Koenig at online dot de
2005-02-16 22:55 ` rth at gcc dot gnu dot org
2005-02-17 3:45 ` Thomas dot Koenig at online dot de [this message]
2005-02-17 10:16 ` [Bug target/19974] " rth at gcc dot gnu dot org
2005-02-17 13:27 ` rth at gcc dot gnu dot org
2005-02-17 13:41 ` pinskia at gcc dot gnu dot org
2005-02-17 15:47 ` Thomas dot Koenig at online dot de
2005-02-17 18:12 ` Thomas dot Koenig at online dot de
2005-03-31 21:38 ` rth 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=20050216205110.5596.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).