Re: Integer-only mode?

--- In sqlite-F5Bj5G+ccuY@xxxxxxxxxxxxxxxx, "jim_lyon_" <jplyon@xxxx> wrote:
> --- In sqlite-F5Bj5G+ccuY@xxxxxxxxxxxxxxxx, "hardinginst" <ambw@xxxx> wrote:
> > In our embedded port of SQLite we do not require floating point 
> > support.  Looking through the code, I don't see an easy way of 
> > eliminating the floating point code, but we may have a go at it.
> 
> Why do you want to rip out the floating point stuff? Is it sqlite's 
> size, speed, or another reason? My first instinct is that you could 
> more easily trim size by aggressively using compiler or linker 
> options, unless the floating point stuff linked in is larger than I 
> think. (You can test this by compiling without linking in floating 
> point code. The executable won't work, of course, but you'll find 
out 
> how much the size would change.) Or perhaps remove a feature you 
> don't use, such as triggers. Often this only means removing a 
single 
> file and some minor patching.
> 
> If it's speed you're after, you'll probably find that most of the 
> time is spent in file i/o and memory/string manipulation. Efforts 
> there can often produce an order of magnitude or more for a 
specific 
> app.
> 
> What does size profiling show for you? I've only looked at speed.
> 
> Jim Lyon

It is an embedded application, and a lot of embedded processors do 
not support floating point in hardware.  The emulation of the 
floating point can be quite slow and adds a large library so it does 
have an effect.  Our application does not store FP numbers either.

I'm thinking that adding some preprocessor defines like:
#define float long
#define double long
#define strtod atol

might do the trick.  Any other ideas?

Thanks.


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/EbFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
sqlite-unsubscribe-VgYJa0VH1e9BDgjK7y7TUQ@xxxxxxxxxxxxxxxx

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/