From: Jakub Jelinek <jakub@redhat.com>
To: Steven Munroe <munroesj@us.ibm.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Update ppc ulps
Date: Sun, 24 Sep 2006 20:49:00 -0000 [thread overview]
Message-ID: <20060924204917.GW4556@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <4516E681.8000903@us.ibm.com>
On Sun, Sep 24, 2006 at 03:11:45PM -0500, Steven Munroe wrote:
> >I'm getting on both ppc and ppc64 2.125 ulp error on clog10 (> 2ulp
> >allowed), 0.75ulp on y0 1/8 and 1ulp on imag csinh (-2-3i).
> >
> Which gcc are you using? I found that gcc-4.2 or gcc-4.1.1 with the
> reassociation patch backport causes upls errors in ppc that are not
> there for just gcc-4.1.1.
I have reassoc backport in. That's one of the reasons why I haven't
regenerated the ulps, just merged, so that both vanilla 4.1.x, 4.1.x
with reassoc etc. pass. While in the above 4 cases gcc with reassoc
generates worse code, for several ones there is an improvement too.
Jakub
prev parent reply other threads:[~2006-09-24 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 10:13 Jakub Jelinek
2006-09-24 20:18 ` Steven Munroe
2006-09-24 20:49 ` Jakub Jelinek [this message]
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=20060924204917.GW4556@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=munroesj@us.ibm.com \
/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).