From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Henderson <rth@twiddle.net>
Cc: libc-ports@sourceware.org
Subject: Re: [alpha] Re-fix imaxdiv
Date: Thu, 24 May 2012 20:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205242052530.19328@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4FBE9EA2.6030207@twiddle.net>
On Thu, 24 May 2012, Richard Henderson wrote:
> Originally fixed in 2001, broken in 2004. Clearly I should have added
> the abilist files a long time ago.
Clearly we need testcases in libc for ldiv, lldiv and imaxdiv as well (we
only seem to have testdiv.c, testing (to a limited extent) div but none of
the others), as tests trying to use the function would presumably have
detected this as well ... interested in adding some?
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2012-05-24 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 20:48 Richard Henderson
2012-05-24 20:54 ` Joseph S. 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=Pine.LNX.4.64.1205242052530.19328@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=rth@twiddle.net \
/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).