From: Carlos Munoz <carlos@kenati.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Denis Vlasenko <vda@ilport.com.ua>,
Lee Revell <rlrevell@joe-job.com>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: How can I link the kernel with libgcc ?
Date: Fri, 10 Mar 2006 12:04:56 -0800 [thread overview]
Message-ID: <4411DBE8.2070302@kenati.com> (raw)
In-Reply-To: <20060310191842.GY27946@ftp.linux.org.uk>
Al Viro wrote:
>On Fri, Mar 10, 2006 at 10:03:58AM -0800, Carlos Munoz wrote:
>
>
>>> ydef[22] = (u_int32_t)(log10((double)(over & 0x0000003f)) /
>>> log10(2));
>>>
>>>
>
>You've got to be kidding. Let's take a good look at that expression:
>log10(x)/log10(2) is what? Right, base-2 logarithm of x. Then you cast
>it to unsigned, i.e. round it down. In other words, you want to know the
>highest bit in (over & 0x3f). Which is to say, (fls(over & 0x3f) - 1).
>Sigh...
>
>
Hi Al,
You are right, so easy. I will look at the data sheet and make sure the
same approach can be applied to all places calling for log10
calculations. I wonder why the data sheet calls for log10 calculations.
It threw me off... should have know better though.
Thanks,
Carlos Munoz
next prev parent reply other threads:[~2006-03-10 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 1:44 How can I link the kernel with libgcc ? Carlos Munoz
2006-03-10 1:45 ` Valdis.Kletnieks
2006-03-10 2:06 ` Lee Revell
2006-03-10 3:01 ` Carlos Munoz
2006-03-10 3:22 ` Lee Revell
2006-03-10 3:25 ` Carlos Munoz
2006-03-10 3:25 ` Lee Revell
2006-03-10 3:47 ` Carlos Munoz
2006-03-10 10:37 ` Denis Vlasenko
2006-03-10 11:05 ` Bart Hartgers
2006-03-10 18:03 ` Carlos Munoz
2006-03-10 18:33 ` linux-os (Dick Johnson)
2006-03-10 18:41 ` Ben Slusky
2006-03-10 19:18 ` Al Viro
2006-03-10 20:04 ` Carlos Munoz [this message]
2006-03-10 10:18 ` Jes Sorensen
2006-03-10 18:07 ` Carlos Munoz
2006-03-10 8:01 ` Arjan van de Ven
2006-03-10 2:02 ` Lee Revell
[not found] <5OEVB-3GX-15@gated-at.bofh.it>
2006-03-10 2:32 ` Robert Hancock
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=4411DBE8.2070302@kenati.com \
--to=carlos@kenati.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=vda@ilport.com.ua \
--cc=viro@ftp.linux.org.uk \
/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