From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] libsbc refactoring
Date: Tue, 17 Jan 2006 15:01:05 -0700 [thread overview]
Message-ID: <43CD6921.9060603@xmission.com> (raw)
Victor,
I've been meaning to try to simplify the 64-bit fixed point by
eliminating the struct that combines two 32-bit values. So now we depend
on the compiler to do all 64-bit math. The arm assembly goes out.
Can you try this and make sure it's still performing well on arm?
This makes all the different flavors of math look the same in the basic ops:
#define SBC_FIXED_0(val) {val = 0;}
#define ADD(dst, src) {dst += src;}
#define SUB(dst, src) {dst -= src;}
#define MUL(dst, a, b) {dst = (sbc_fixed_t)a * b;}
#define MULA(dst, a, b) {dst += (sbc_fixed_t)a * b;}
so we could even eliminate these macros. I know Marcel would be happy to
see them go ;)
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
next reply other threads:[~2006-01-17 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 22:01 Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 12:44 [Bluez-devel] libsbc refactoring Victor Shcherbatyuk
2006-01-19 16:36 ` Brad Midgley
2006-01-19 21:23 ` Victor Shchebatyuk
2006-01-19 21:36 ` Brad Midgley
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=43CD6921.9060603@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).