From: "Joseph S. Myers" <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Cc: <codonell@redhat.com>, <schwab@linux-m68k.org>,
<david.holsgrove@xilinx.com>, <cmetcalf@tilera.com>,
<kkojima@rr.iij4u.or.jp>, <davem@davemloft.net>
Subject: Arch maintainers: please regenerate libm-test-ulps for 2.19
Date: Fri, 24 Jan 2014 18:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1401241756580.9799@digraph.polyomino.org.uk> (raw)
The following architectures do not appear to have had libm-test-ulps
regenerated for 2.19:
hppa
m68k (for coldfire, copying sysdeps/mips/mips32/libm-test-ulps to
sysdeps/m68k/coldfire/libm-test-ulps and removing the existing
sysdeps/m68k/coldfire/fpu/libm-test-ulps should be a reasonably safe
bet, in the absence of proper regeneration)
microblaze (also has a file libm-test-ulps_new, which should simply be
removed)
tile
sh (I also suggest moving the file from sysdeps/sh/sh4/fpu to sysdeps/sh,
as ulps for SH4 with FPU should be a superset of those for other
variants)
sparc
Please truncate the existing file to empty, run "make regen-ulps", remove
any excessively large ulps from the file (as well as ulps for functions
such as sqrt or fma that shouldn't have any, I'll let you know if any such
ulps were left in), file bugs for any such cases if not already filed, and
commit the updated file.
Some indication of expected test results at
<https://sourceware.org/glibc/wiki/Release/2.19> would also be welcome.
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2014-01-24 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 18:07 Joseph S. Myers [this message]
2014-01-24 18:51 ` Chris Metcalf
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=Pine.LNX.4.64.1401241756580.9799@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmetcalf@tilera.com \
--cc=codonell@redhat.com \
--cc=davem@davemloft.net \
--cc=david.holsgrove@xilinx.com \
--cc=kkojima@rr.iij4u.or.jp \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=schwab@linux-m68k.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).