[ Home | Articles | Account | People | Projects | FAQ ] DEV300_m19 (and m68k)
The DEV300_m19 callcatcher logs show a small but steady shrinkage improvement as more cleanup patches make their way into head.
In other news, I ported uno to m68k so OOo3 builds and functions on m68k under qemu. The sight of a running m68k OOo is somehow incredibly amusing.
DEV300_m17
Latest callcatcher results DEV300_m17 show a modest improvement as unused hwpfilter patch gets integrated, though there’s still an unused destructor, pointing more towards a potential resource leak where it should be used rather than get removed.
DEV300_m14 callcatcher
And DEV300_m14 results are available, with the integration of the binfilter fixes (thanks mba) unused symbol count has halved since DEV300_m13 and tumbles down the charts. I’ve extended callcatcher to understand basic map files so it can be used on non-terminal modules which have map files. Which extends the coverage to a further 25 modules.
one of those weeks
See as gcc ate my starbasic with -fno-strict-aliasing it prompted me to check if we still need -fno-strict-aliasing anyway given all the warning cleanups of the last year. The short answer is definitely :-), but it looks doable to make it possible, and I’ve gotten it to at least launch with -fstrict-aliasing which should be sufficient to do some measurements on it next week to see if there is any measurable difference. Unfortunately while I can (probably) make Ooo -fstrict-aliasing good there are a gadzillion warnings from the stlport headers used on i386 builds so unless stlport was bumped up to one of the later versions where the warnings are fixed (or stlport dropped and gcc’s stl used like we did for x86_64) then only non-i386 users could get the benefit.
Some other random thoughts to look at to see if they’d matter a damn are:
arm eabi
As mentioned here in November I resuscitated Peter Naulls’s ARM oabi port of OOo 1.X.Y for 2.X.Y and extended it for ARM eabi and built some fedora rpms under qemu that functioned under that environment. I was sort of sceptical that they would actually fit into and work on a Nokia device, (not actually having one myself) but after a five day build (as rene tells me) for Debian armel, apparently it does actually work on an N800. Most excellent.
DEV300_m13 callcatcher
I extended callcatcher to understand linker map files, so the scan can be expanded to also include OOo modules which export symbols for external use and report on unexported symbols which are unusable outside the .so and unused within it., which means that configmgr decloaks and appears in the top four dead-code list.. DEV300_m13 results.
dead code list
Up to date lists of the currently unreferenced symbols in OOo are available here. Currently 2823 methods, though a lot of these should go away when the submitted patches filter through.
OOo gio integration
So I finished off Jan’s initial gio OpenOffice.org integration work (i.e. issue 88090 as workspace ucpgio1)
The gio api is a far better fit to the OOo worldview than gnome-vfs is and was pretty straightforward to implement modulo my own bafflement as to why I had an error claiming that mounting share named “X” failed as not existing which incredibly had the root cause that the share named “X” was really called “Y”.
GoOOoCon08
The GoOOoCon08 Presentation that I gave.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!
