From: Ian Lance Taylor <iant@google.com>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: gcc@gcc.gnu.org
Subject: Re: glibc 2.7 complex functions are possibly miscompiled by gcc 4.3 trunk
Date: Sat, 29 Dec 2007 18:12:00 -0000 [thread overview]
Message-ID: <m3fxxl1jdy.fsf@localhost.localdomain> (raw)
In-Reply-To: <200712291811.47936.ismail@pardus.org.tr>
Ismail Dönmez <ismail@pardus.org.tr> writes:
> Saturday 22 December 2007 19:11:32 tarihinde Ismail Dönmez şunları yazmıştı:
> > 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
>
> Replying to myself once again, these failures are due to -fgcse-after-reload
> flag, -O3 -fno-gcse-after-reload cures this. Any tips on how to debug this?
Generic advice to start: compile with -da to get all the RTL dump
files. Compare the dump files immediately before and after
gcse-after-reload and see what changed. Set breakpoints on
validate_change or make_insn_raw as appropriate for the changes. Walk
up the stack and see what the code is doing. The file in question is
postreload-gcse.c, which is relatively self-contained.
Of course it is moderately likely that the bug is not in
gcse-after-reload, and is in some other pass generating incorrect
information. Still, finding the problem in gcse-after-reload is a
good start.
Ian
next prev parent reply other threads:[~2007-12-29 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 18:14 Ismail Dönmez
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 [this message]
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=m3fxxl1jdy.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=ismail@pardus.org.tr \
/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).