Quote:
Originally Posted by dima_tr
Marcel, can you please check the performance change when using the libsqlite3.so.0 attached? The QEMU works OK with it.
SQLite3, Version 3.7.5, http://www.sqlite.org/sqlite-amalgamation-3070500.zip Amalgamation (gives about 5-10% better performance) + built with some optimization flags. See the build script. |
why is the library so big? Analyzing the DR800 2.0RC3 library it looks it's version 3.5.2:
libsqlite3.so.0.8.6 -> 375544 vs. libsqlite3.so.0 -> 857224 bytes
Anyway, that performance improvement is interesting.
/me thinking if upgrading glib could be useful too...
I've spent (well, wasted) some hours trying ty compile the recently released v1.0 of pcc (a compiler, like gcc, [1]) for my DR devel environment, in order to check if the resulting DR binaries could run faster that the ones with gcc.
pcc is not supported for linux + ARM processors, but it is for NetBSD + ARM so I thought it wouldn't be so hard... I was mistaken...
DR800 and DR1000 share the same processor ([2], [3]): FreeScale i.MX31 (ARM1136JF-S, [4]).
@dima_tr: could you repeat your tests with these new arguments to gcc:
-march=arm1136jf-s -mtune=arm1136jf-s
Btw, Mackx, I think you work as C developer for embeded devices so maybe you can explain us if it's worth to build a newer gcc or pcc cross-compilers?
would we get any speed difference in the binaries? Devel env includes gcc v4.3.0. but gcc v4.4 and v4.5 changes notes ([5], [6]) list some performance improvements for ARM processors.
Iņigo
[1]
http://pcc.ludd.ltu.se/
[2]
https://wiki.mobileread.com/wiki/DR800SG
[3]
https://wiki.mobileread.com/wiki/IRex_Digital_Reader
[4]
http://www.freescale.com/webapp/sps/...sp?code=i.MX31
[5]
http://gcc.gnu.org/gcc-4.4/changes.html
[6]
http://gcc.gnu.org/gcc-4.5/changes.html