From: Ulrich Drepper <drepper@gmail.com>
To: libc-hacker@sourceware.org
Subject: x86-64 log
Date: Sun, 16 Oct 2011 02:27:00 -0000 [thread overview]
Message-ID: <CAOPLpQfJv6eqAThbUGAW5e_C0fH+2RxR1Fu3Bnj=YO3CGHZJ=g@mail.gmail.com> (raw)
I've removed the special case for values close to 1.0 from the x86-32
log and logf handling. I know the logf change is safe, I checked
every value. But the search space for log is too large. I looked at
the closest 1 billion values to both sides of 1.0, which are the
critical ones. Everything checked out.
I think at least on modern hardware everything is safe. If problems
pop up due to old hardware we might have to conditionalize the
changes.
reply other threads:[~2011-10-16 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOPLpQfJv6eqAThbUGAW5e_C0fH+2RxR1Fu3Bnj=YO3CGHZJ=g@mail.gmail.com' \
--to=drepper@gmail.com \
--cc=libc-hacker@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).