public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: gcc@gcc.gnu.org
Subject: glibc 2.7 complex functions are possibly miscompiled by gcc 4.3 trunk
Date: Sat, 22 Dec 2007 18:14:00 -0000	[thread overview]
Message-ID: <200712221911.32786.ismail@pardus.org.tr> (raw)

Hi all,

I am doing glibc 4.3 regression tests using gcc 4.3 trunk nearly every day and 
I see 3 tests fail :

math/test-float
math/test-ildoubl
math/test-ifloat

The erorrs are all similar :

Failure: Test: Imaginary part of: cacosh (-0 + 0 i) == 0.0 + pi/2 i
Result:
 is:          0.00000000000000000000e+00   0x0.00000000000000000000p+0
 should be:   1.57079637050628662109e+00   0x1.921fb600000000000000p+0
 difference:  1.57079637050628662109e+00   0x1.921fb600000000000000p+0
 ulp       :  13176795.0000
 max.ulp   :  0.0000

All of the imaginary part checks fail, with the help of GFortran maintainers 
we identified 2 testcases which fail with glibc 2.7 when compiled with gcc 
4.3 trunk [0] .

This problem also causes 32 unexpected failures on gfortran regression tests. 
So I wonder if you guys can help me debug this, I checked out libc sources 
but its mostly assembly stuff for math functions. Maybe Jakub has an idea, 
not sure.

Any help/comment appreciated.

[0] http://sourceware.org/bugzilla/show_bug.cgi?id=5490

Regards,
ismail


-- 
Never learn by your mistakes, if you do you may never dare to try again.

             reply	other threads:[~2007-12-22 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 18:14 Ismail Dönmez [this message]
2007-12-28 22:47 ` Ismail Dönmez
2007-12-29  6:32   ` Ismail Dönmez
2007-12-29 17:49 ` Ismail Dönmez
2007-12-29 18:12   ` Ian Lance Taylor
2007-12-29 18:23     ` Ismail Dönmez

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=200712221911.32786.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=gcc@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).