From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] 32-bit sbc now in CVS
Date: Sat, 28 Jan 2006 23:30:44 -0700 [thread overview]
Message-ID: <43DC6114.70103@xmission.com> (raw)
guys
FYI, I worked through the scaling to get 32-bit decoding to work. I
committed this and made the 32-bit encoder/decoder the default when you
enable fixed-point.
It turns out that we are counting on undefined compiler behavior in
several places.
signed_var >> x
Is not necessarily defined to perform an arithmetic shift. It *could* be
replaced by:
signed_var / (1 << x)
And while this will always produce the correct value, we can't count on
it being performed optimally (ie, it could really generate a heavyweight
division op)
I'm inclined to leave it as-is. Maybe there's an autoconf test to
confirm this compiler behavior, boiling down to:
ASSERT(-2 >> 1 == -1)
Brad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-01-29 6:30 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=43DC6114.70103@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.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 NNTP newsgroup(s).