From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] libsbc refactoring
Date: Thu, 19 Jan 2006 09:36:37 -0700 [thread overview]
Message-ID: <43CFC015.80005@xmission.com> (raw)
In-Reply-To: <C70061B183DE09419568AB2060C52A95017EAF33@arion.intra.local>
Victor
> I think there were macros relying on the copiler to handle 64-bit math
> and, as I remember, it was 2 times slower than arm specific code. But
> I'll check anyway. Altough 32-bit math should be enough, but it probably
> needs some good thinking and smart tricks (or may be not).
I want to have a look at unifying on 32-bit but I was hoping this would
be ok to clean things up a bit.
I can see why assembly would be better than working with two 32-bit
values. You don't have a way to get at the add-with-carry assembly
instruction for example. But the compiler has got to be doing something
wrong if basic math ops on a native c type (int64_t) are only half as
fast as hand-coded assembly. :(
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 prev parent reply other threads:[~2006-01-19 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 12:44 [Bluez-devel] libsbc refactoring Victor Shcherbatyuk
2006-01-19 16:36 ` Brad Midgley [this message]
2006-01-19 21:23 ` Victor Shchebatyuk
2006-01-19 21:36 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 22:01 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=43CFC015.80005@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).