From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] libsbc refactoring
Date: Thu, 19 Jan 2006 14:36:42 -0700 [thread overview]
Message-ID: <43D0066A.6030803@xmission.com> (raw)
In-Reply-To: <1137705822.393.4.camel@localhost.localdomain>
Victor
I will roll it back if we know that is happening with gcc.
If it isn't too hard to modify the arm assembly for doing the basic ops
using an int64_t instead of the int32_t/uint32_t I'd like to see that.
Where should I pick up with the 32-bit code? I think I saw this in a header
#define SP4(val) (val >> SCALE_PROTO4_TBL)
and I was thinking it should look more like
#define SP4(val) (((int32_t)val)/(1<<SCALE_PROTO4_TBL))
To preserve negative values. Does that seem reasonable? I didn't do
anything with this idea yet.
I think the (int32_t) cast was necessary because the tables use a
positive-looking hex constant for negative values.
Brad
> I think (may be mistakenly) gcc does not use all the optimizations, only
> generic ones and, probably, the 32x32 -> 64 register multiplication is
> not among them. It might be that the arm compiler does this kind of
> optimizations, but it needs licensing I guess.
>
> Regards,
> Victor.
-------------------------------------------------------
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 21: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
2006-01-19 21:23 ` Victor Shchebatyuk
2006-01-19 21:36 ` Brad Midgley [this message]
-- 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=43D0066A.6030803@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).