From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Regenerate ULPs for i486 builds.
Date: Fri, 28 Oct 2016 12:48:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610281245320.32491@digraph.polyomino.org.uk> (raw)
In-Reply-To: <8f606007-c4fc-70a1-13ca-509f1b2f131c@redhat.com>
On Thu, 27 Oct 2016, Carlos O'Donell wrote:
> Why might we be 1-3 ULP worse than the previously checked in baseline?
Because, for the most part, when new tests or libm changes require ulps
updates, people test for i686/fpu/multiarch and so update that file but
not this one (the two can have slightly different results for some
functions because of the different implementations used). The new tests
requiring this update were from commit
c898991d8bcfacc825097ba389ffccc5367c2b2d.
> OK to checkin?
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-10-28 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 3:02 Carlos O'Donell
2016-10-28 12:48 ` Joseph Myers [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=alpine.DEB.2.20.1610281245320.32491@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).